Hi,
Oh, this makes me think: how would one fix something like this?
The wiki page already contains some answer:
https://wiki.openstack.org/wiki/Python3#Common_patterns
Don't hesitate to complete the page if needed.
See also my personal list of documents:
On 04/24/2015 10:20 PM, Kevin L. Mitchell wrote:
On Fri, 2015-04-24 at 16:07 -0400, Sean Toner wrote:
What I meant by the worst of both worlds is that you don't get the nice
new features of python3, while simultaneously dealing with the headaches
of making code run under both python versions.
Hi,
I wrote a spec to port Nova to Python 3:
https://review.openstack.org/#/c/176868/
I updated my spec to take in account all comments. Example of changes:
- Explicitly say that Python 2 support is kept (ex: change the title to Adding
Python 3.4 support to Nova)
- Clarify what are the
Hi,
Porting OpenStack applications during the Liberty Cycle was discussed last days
in the thread [oslo] eventlet 0.17.3 is now fully Python 3 compatible.
I wrote a spec to port Nova to Python 3:
https://review.openstack.org/#/c/176868/
I mentioned the 2 other Python 3 specs for Neutron
Maybe we can add a python3 jenkins job (non-voting) to help us finding out
some potential issue.
2015-04-24 16:34 GMT+08:00 Victor Stinner vstin...@redhat.com:
Hi,
Porting OpenStack applications during the Liberty Cycle was discussed last
days in the thread [oslo] eventlet 0.17.3 is now
Hi,
If written to use python 3, I hope it will use all the new features of
python 3.4 moving forward.
The spec adds Python 3 support, but it keeps Python 2 support. It's too early
to drop Python 2, Nova is deployed everywhere with Python 2.
For example, argument annotations, coroutines,
If written to use python 3, I hope it will use all the new features of
python 3.4 moving forward.
For example, argument annotations, coroutines, asyncio, etc. At my last
workplace, we tried to make our project python2 and 3 compatible (ie,
you could run it under 2.7 or 3.3+) but this was the
Sean Toner wrote:
If written to use python 3, I hope it will use all the new features of
python 3.4 moving forward.
For example, argument annotations, coroutines, asyncio, etc. At my last
workplace, we tried to make our project python2 and 3 compatible (ie,
you could run it under 2.7 or 3.3+)
Excerpts from Sean Toner's message of 2015-04-24 05:38:42 -0700:
If written to use python 3, I hope it will use all the new features of
python 3.4 moving forward.
For example, argument annotations, coroutines, asyncio, etc. At my last
workplace, we tried to make our project python2 and 3
On 4/24/15 4:18 PM, Sean Toner wrote:
On Friday, April 24, 2015 11:20:03 AM Joshua Harlow wrote:
Sean Toner wrote:
If written to use python 3, I hope it will use all the new features
of python 3.4 moving forward.
For example, argument annotations, coroutines, asyncio, etc. At my
last
On Friday, April 24, 2015 11:20:03 AM Joshua Harlow wrote:
Sean Toner wrote:
If written to use python 3, I hope it will use all the new features
of python 3.4 moving forward.
For example, argument annotations, coroutines, asyncio, etc. At my
last workplace, we tried to make our
On Friday, April 24, 2015 09:13:14 AM Victor Stinner wrote:
Hi,
If written to use python 3, I hope it will use all the new features
of python 3.4 moving forward.
The spec adds Python 3 support, but it keeps Python 2 support. It's
too early to drop Python 2, Nova is deployed everywhere
On Fri, 2015-04-24 at 16:07 -0400, Sean Toner wrote:
What I meant by the worst of both worlds is that you don't get the nice
new features of python3, while simultaneously dealing with the headaches
of making code run under both python versions. You'll have to do weird
things with imports
Sean Toner wrote:
On Friday, April 24, 2015 11:20:03 AM Joshua Harlow wrote:
Sean Toner wrote:
If written to use python 3, I hope it will use all the new features
of python 3.4 moving forward.
For example, argument annotations, coroutines, asyncio, etc. At my
last workplace, we tried to make
14 matches
Mail list logo
