Django just release their 1.5 version.
It now supports Python 3, my question is quite simple indeed: With this 1.5 Version, should I still use Python 2.7 or Python 3 ? I assume that with Python 3 there will be some issues with 3rd parties app no ?
In your case, what would you do ?
The release notes state clearly that Python 3 support in 1.5 is experimental. And yes, third-party apps will be a problem.
If I was starting a new development which I didn't expect to go live until well after version 1.6 is released (when Python 3 support is supposed to be production ready, and hopefully the 3rd party apps have caught up) , then yes, I would go with Python 3. It is significantly cleaner than Python 2.7.
But if you want your site up and running in the near future, stick with 2.7.
I would still use python 2.7 because many apps and libraries are not ready for python 3.x
PIL is not working correctly with python 3
Related
The company I'm working for is still in the process of going over from Python 2.7 to Python 3, so I'm stuck with Python 2.7 even though it is officially already end of life.
For a project I'm looking into grpc, but I see that the latest versions do not support Python 2.7 anymore.
But since I'm stuck with Python 2.7 my question is simple: what is the latest version of grpcio which still supports Python 2.7?
You can find the supported version in PyPI pages. On the bottom left corner, if there is a "2.7" tag in the "Classifiers" section, that means 2.7 is supported. Using this method, we can find the latest grpcio version for 2.7 to be v1.39.0: https://pypi.org/project/grpcio/1.39.0/
Currently my project is using in old python version 2.7 and in order to keep track of source code complexity, git pre-commit hook, HTML Graph report of work I would like to use python pip tool wily.
However, since pip wily support only python 3, I am looking for way I could install it for my current project implementing python 2.7. How could I install it for python 2.7?
One workaround solution I could think of is to set up a separate python 3 virtual environment for wily and check python 2.7 source code, it is possible? Thanks
AFAIU the project requires Python 3. At Oct 14, 2018 (a year ago now) the author formally declared that the project requires Python 3.6+.
If I want to run Python inside ATOM, I have to always disable PlatformIO and restart ATOM again, so it works fine. I managed to avoid that pain by pointing my installed Python packages to run Python 3, instead of the standard Python (Python 2), But I really wish I could understand what's happening so I could use any of the versions freely, as I need. Any light on the subject?
My system Is Linux(mint 19)
Thanks!!!
It sounds like your default Python is 2.7, but everything is installed against Python 3, and Atom always uses Python 2. You can fix this by changing the default Python that is used by Atom.
For one off uses, try How to configure Atom to run Python3 scripts? and for permanently changing the version of Python for Atom, have a look at How to setup Atom's script to run Python 3.x scripts? May the combination with Windows 7 Pro x64 be the issue? (despite Windows 7 Pro in the title, the solution applies to Atom in general).
How can I choose the appropriate version of Python runtime to use along with TensorFlow 1.0 ?
I would invite you to check the TensorFlow installation page which gives all the detail for your specific system. At the moment, TensorFlow supports Python 2.7, 3.4, 3.5, 3.6, although it seems 3.6 does not yet have GPU support. If you're starting out with Python, you should probably get 3.5 (if you need GPU) or 3.6 (if you'll only use CPU). Python 2.7 was released a long time ago.
If you don't already have Python, you can get it from the Python website. However, I recommend you get Python through Anaconda so that you get all necessary packages to run things like TensorFlow.
It seems they all run on Python 2.x.
(Actually I want a more widely-used engine that has Python 3.x support.)
Just released Jinja 2.3 has experimental support for Python 3. http://lucumr.pocoo.org/2010/2/10/jinja-2-3-released
If you don't mind using beta software, the newly-released moody-templates was written for Python 3 from the ground up.
https://github.com/etianen/moody-templates
Maybe very outdated, but Mako supports python 3.
The first search result is the templating wiki page; which includes at least one templating engine which says it works on Python 2.4, 2.5, 2.6 and 3.0.