I finally want to migrate a Django project to Python 3.3 but have some issues with django-compressor, because it is not Python 3 compatible (yet).
Out of the asset managers listed on https://www.djangopackages.com/grids/g/asset-managers/ these seem interesting to me, since they support CSS/LESS too:
https://www.djangopackages.com/packages/p/webassets/
https://www.djangopackages.com/packages/p/django-pipeline/
https://www.djangopackages.com/packages/p/django-gears/
I have multiple CSS and LESS files, and a lot of JavaScript files which need to be minified, and Python 3.3 must be supported. What would you recommend for my use case? Are there other, better suited projects around?
I recommend to use a django-pipeline. It supports python 3 and do what it should do. I used it for one of my project ( but it was python 2.7) and perfectly happy with it.
Related
Disclaimer:
First, I apologise if I'm incorrectly applying technical terms here or, worse, completely misunderstanding things. I'll edit if corrected.
Context:
Lately I've been building and deploying some basic website ideas to Heroku using the Django framework. I've been doing this on Windows, using venv as my virtual environment "wrapper". I've been building these exclusively from the command line interface.
I also have a MacBook that I'd like to use to access and manage those websites, and in future, larger projects. I would prefer not to install Windows on this MacBook.
To be clear, I know that it's possible to build and deploy a website using Django and Heroku on macOS. I know there are, at the very least, some syntactical differences in how I would approach this from the CLI versus Terminal.
Desired outcome:
I would like to set up a website in the fashion indicated above on Windows or macOS, and then access and manipulate it from the other OS.
Questions:
Is this possible? (Or if I set it up on Windows must I only use Windows to manage it?)
If I set up a website in this fashion using Django, Heroku, and venv on Windows, how (if at all) might I then access and manipulate that website from macOS? I think what I'm mostly stuck on is that, as far as I can tell, I can't use the same virtual environment on both Windows and macOS (I believe venv is itself Windows-only).
Is it possible to "wrap" my website in both venv (Windows) and virtualenv (macOS)?
Am I correct in thinking the only real (i.e. non-syntactical) difference that I need to account for is the virtual environment itself?
--
Sorry if I have massive gaps in my knowledge. I'm self-taught and have historically been terrible at asking for help. I'm trying to fill the gaps by improving my question-asking.
Finally, I suspect that the fact I'm using Heroku may be irrelevant, but I'm including that information in case I am mistaken.
Yes, for most of the projects, you will be able to develop your Django web site on Windows, MacOS and Linux simultaneously. Your virtual environment "wrapper" doesn't really matter, you will use or install and use the one you like or available on your OS.
Then you will learn about Docker.
Looks like there three connector nuget packages available from steeltoe https://www.nuget.org/packages/Steeltoe.Connector.ConnectorCore/
https://www.nuget.org/packages/Steeltoe.Connector.CloudFoundry/
https://www.nuget.org/packages/Steeltoe.CloudFoundry.ConnectorCore/. I have an ASP.NET Core application in .net core 3.1. Which one I should select now? Also can i get detailed documentation of each of these packages. Looks like Steeltoe.Connector.ConnectorCore need .netcore3.1 and the other two simply requires .nestandard2.0. Any idea why is it so? Ideally all reusable libraries target .netstandard2.X, if I am not wrong
For Steeltoe 3.0 use Steeltoe.Connector.ConnectorCore and Steeltoe.Connector.CloudFoundry - https://steeltoe.io/docs/3/connectors/usage#cloud-foundry
For Steeltoe 2.x use Steeltoe.CloudFoundry.ConnectorCore.
As far as the targeting goes, Steeltoe 3.0 is focused on .NET Core 3.1+, so we aren't intentionally building compatibility for anything older on that branch. There may be some cases where we're targeting netcoreapp3.1 and could be targeting netstandard2.0... We've already dialed back several packages, though it doesn't look like ConnectorCore has been adjusted yet, we'd have to look at it to see if we can.
If you use anything that came before .NET Core 3.1, you should use Steeltoe 2.x, which is still maintained.
I am using some Cocoapods packages that works well in Swift 3.2. If I changed those packages I need to do lot of code editing which will consume lot of time and effort. Is there any ways to add Swift 3 to Xcode 11?
I doubt you can ADD a Swift version. I.e. use 5.1 for your code and 3.1 for libraries. AFAIK, all binaries have to be built using the same compiler.
Technically, you can CHANGE the toolchain. This article illustrates how (not sure if nowadays 3.1 is stretching this though):
Medium Blog about Xcode toolchains
However, I doubt that you can submit apps built with 3.1 to the AppStore.
I also wonder if you really even want to try to buy into this. If you use Swift 3.1 you may need to make sure to bundle the runtime with your app. Since one of the more recent evolutions of iOS, the Swift runtime is not packaged with apps anymore, but relies on the OS runtime.
Good luck on this endeavor. Really want to kick all the Swift 5.x goodies? ;)
We are just starting some cloud-based apps based on Python + Django and we have a small dilemma. At first we decided to go with Python 3.3, but than we saw that a lot of libraries/modules have not been ported yet, thus we might have to do extra work to make sure that everything works with Python 3.3.
Given the fact that the projects that we are starting will have a time frame of a few years what advice would you give us? To go with Python 2.7 or Python 3.3?
Thanks in advance!
Go with Python 2.7 for now. Make sure that your code translates cleanly when using 2to3. When the modules are available for Python 3.x, translate your code and run with it.
I heard about lots of compatibility issues with PostgreSQL and Django + psycopg2.
What would be the recommended latest and greatest versions that are fully compatible for a new Django project starting from scratch?
The bug is not critical: it only affects database creation during tests: https://code.djangoproject.com/ticket/16250 There should be no other problem between psycopg and django.
The problem can be avoided using psycopg 2.4.1, but there have been several bug fixes since then, so I'd rather apply some simple patch to django to make the two play well together.
BTW I wonder when will they release django 1.3.2: the bug is been there for 6 months now...