I have updated it. Thank you for sharing a link.
On Mon, Jul 27, 2015 at 3:44 PM, Victor Stinner vstin...@redhat.com wrote:
Hi,
On 27/07/2015 12:35, Roman Vasilets wrote:
Hi, just what to share with you. Rally project also have voting py34
jobs. Thank you.
Cool! I don't know if Rally
Hi,
On 27/07/2015 12:35, Roman Vasilets wrote:
Hi, just what to share with you. Rally project also have voting py34
jobs. Thank you.
Cool! I don't know if Rally port the Python 3 is complete or not, so I
wrote work in progress. Please update the wiki page if the port is done:
Thomas,
1.56 of python-memcached with haypo's fix was released yesterday.
-- dims
On Mon, Jul 27, 2015 at 4:53 AM, Thomas Goirand z...@debian.org wrote:
On 07/20/2015 08:26 PM, Brant Knudson wrote:
On Fri, Jul 17, 2015 at 7:32 AM, Victor Stinner vstin...@redhat.com
Hi, just what to share with you. Rally project also have voting py34 jobs.
Thank you.
On Fri, Jul 17, 2015 at 2:32 PM, Victor Stinner vstin...@redhat.com wrote:
Hi,
We are close to having a voting py34 gate on all OpenStack libraries and
applications. I just made the py34 gate voting for the
On 07/20/2015 08:26 PM, Brant Knudson wrote:
On Fri, Jul 17, 2015 at 7:32 AM, Victor Stinner vstin...@redhat.com
mailto:vstin...@redhat.com wrote:
Hi,
...
(3) keystonemiddleware: blocked by python-memcached, I sent a pull
request 3 months ago and I'm still waiting...
You can (nearly) add Designate to this list :)
Pradeep has been doing a great job getting the codebase py3 compatible!
Thanks,
Kiall
On 17/07/15 12:32, Victor Stinner wrote:
Hi,
We are close to having a voting py34 gate on all OpenStack libraries and
applications. I just made the py34 gate
: Tuesday, July 21, 2015 12:51:03 PM
Subject: Re: [openstack-dev] Python 3: 5 more projects with a py34 voting
gate, only 4 remaing
You can (nearly) add Designate to this list :)
Pradeep has been doing a great job getting the codebase py3 compatible!
Thanks,
Kiall
On 17/07/15 12:32
On Fri, Jul 17, 2015 at 7:32 AM, Victor Stinner vstin...@redhat.com wrote:
Hi,
...
(3) keystonemiddleware: blocked by python-memcached, I sent a pull request
3 months ago and I'm still waiting...
https://github.com/linsomniac/python-memcached/pull/67
I may fork the project if the
On Fri, Jul 17, 2015 at 7:32 AM, Victor Stinner vstin...@redhat.com wrote:
Hi,
We are close to having a voting py34 gate on all OpenStack libraries and
applications. I just made the py34 gate voting for the 5 following projects:
* keystone
...
Victor
While there's a py34 gate for
Hi,
We are close to having a voting py34 gate on all OpenStack libraries and
applications. I just made the py34 gate voting for the 5 following projects:
* keystone
* heat
* glance_store: Glance library (py34 is already voting in Glance)
* os-brick: Cinder library (py34 is already voting in
On 17 July 2015 at 23:32, Victor Stinner vstin...@redhat.com wrote:
Hi,
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1367907
The bug was fixed in Python 3.4 in May 2014 and was reported to Ubuntu in
September 2014.
I've just queried and its apparently in review-wait in the
On 7/17/2015 6:32 AM, Victor Stinner wrote:
Hi,
We are close to having a voting py34 gate on all OpenStack libraries and
applications. I just made the py34 gate voting for the 5 following
projects:
* keystone
* heat
* glance_store: Glance library (py34 is already voting in Glance)
*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/02/2015 05:15 PM, Jeremy Stanley wrote:
After a long wait and much testing, we've merged a change[1] which
moves the remainder of Python 3.3 based jobs to Python 3.4. This
is primarily in service of getting rid of the custom workers we
On Tue, Mar 3, 2015, at 07:56 AM, Ihar Hrachyshka wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/02/2015 05:15 PM, Jeremy Stanley wrote:
After a long wait and much testing, we've merged a change[1] which
moves the remainder of Python 3.3 based jobs to Python 3.4. This
is
On 2015-02-03 08:15:39 -0500 (-0500), Victor Stinner wrote:
[...]
Debian Testing (Jessie) and Unstable (Sid) provide Python 3.4.2.
[...]
Yep, I'm playing now with the possibility to run jobs on Debian
Jessie, but due to circumstances with the providers who donate
computing resource to us I'm
Hi,
It's good to move forward to Python 3.4 :-)
[2] https://launchpad.net/bugs/1367907
This bug was introduced in Python 3.4.0 and fixed in Python 3.4.1. It's too bad
that Ubunbu Trusty didn't upgraded yet Python 3.4 to 3.4.1 (released 6 months
ago) or 3.4.2. Request to upgrade python 3.4 in
After a long wait and much testing, we've merged a change[1] which
moves the remainder of Python 3.3 based jobs to Python 3.4. This is
primarily in service of getting rid of the custom workers we
implemented to perform 3.3 testing more than a year ago, since we
can now run 3.4 tests on normal
Hi Julien,
2014-02-03 Julien Danjou jul...@danjou.info:
There's https://wiki.openstack.org/wiki/Python3 but it's not (always) up
to date.
Thanks for the pointer, really helpful about the status for the main
projects and some key hints.
The interest never decreased, but it's always have
On Tue, Feb 04 2014, Sylvain Bauza wrote:
Yep, I know there is a team, but from my POV, it seems the visibility of
this group decreased over the last months.
We don't have a marketing subteam yet.
AIUI, there are no more regular meetings on IRC. Ideally, I'm asking for a
team because I
Hi,
I was at the FOSDEM event this week-end and some interesting talks about
asyncio raised my interest about this framework for replacing eventlet.
Although there is an experimental port of asyncio for Python 2.6 named
trollius [1], I think it would be a good move for having Python 3.
I know
On Mon, Feb 03 2014, Sylvain Bauza wrote:
I was at the FOSDEM event this week-end and some interesting talks about
asyncio raised my interest about this framework for replacing eventlet.
Although there is an experimental port of asyncio for Python 2.6 named
trollius [1], I think it would be
On Mon, Feb 3, 2014 at 5:29 PM, Julien Danjou jul...@danjou.info wrote:
Last, but not least, trollius has been created by Victor Stinner, who
actually did that work with porting OpenStack in mind and as the first
objective.
AFAIK: victor had plans to send a mail about it to the list later
Am 24. Juli 2013 18:00:30 schrieb Monty Taylor mord...@inaugust.com:
On 07/23/2013 03:02 PM, Brian Curtin wrote:
On Jul 23, 2013, at 3:51 PM, Eric Windisch e...@cloudscaling.com
mailto:e...@cloudscaling.com
wrote:
On Tue, Jul 23, 2013 at 4:41 PM, Logan McNaughton lo...@bacoosta.com
On 07/23/2013 03:02 PM, Brian Curtin wrote:
On Jul 23, 2013, at 3:51 PM, Eric Windisch e...@cloudscaling.com
mailto:e...@cloudscaling.com
wrote:
On Tue, Jul 23, 2013 at 4:41 PM, Logan McNaughton lo...@bacoosta.com
mailto:lo...@bacoosta.com wrote:
I'm sure this has been asked
On Wed, 2013-07-24 at 09:31 -0700, Alex Gaynor wrote:
I believe Red Hat's new Software Collections things address this issue,
this is to the point which Django (which has historically used RHEL as a
barometer for when we could drop Pythons) will drop 2.6 in our next release.
Yep, that's a very
On Jul 23, 2013, at 4:32 PM, Doug Hellmann
doug.hellm...@dreamhost.commailto:doug.hellm...@dreamhost.com wrote:
On Tue, Jul 23, 2013 at 4:41 PM, Logan McNaughton
lo...@bacoosta.commailto:lo...@bacoosta.com wrote:
I'm sure this has been asked before, but what exactly is the plan for Python
Speaking of preferred ways to port, has there been any discussion about
which version takes precedence when we have to do different things? For
example, with imports, should we be trying the 2.x name first and falling
back to 3.x on ImportError, or vice versa?
Are we having it now? My belief
On Jul 24, 2013, at 1:27 PM, Eric Windisch
e...@cloudscaling.commailto:e...@cloudscaling.com
wrote:
Speaking of preferred ways to port, has there been any discussion about which
version takes precedence when we have to do different things? For example, with
imports, should we be trying the
I'm sure this has been asked before, but what exactly is the plan for
Python 3 support?
Is the plan to support 2 and 3 at the same time? I was looking around for a
blue print or something but I can't seem to find anything.
If Python 3 support is part of the plan, can I start running 2to3 and
On Tue, Jul 23, 2013 at 4:41 PM, Logan McNaughton lo...@bacoosta.comwrote:
I'm sure this has been asked before, but what exactly is the plan for
Python 3 support?
Is the plan to support 2 and 3 at the same time? I was looking around for
a blue print or something but I can't seem to find
On Jul 23, 2013, at 3:51 PM, Eric Windisch
e...@cloudscaling.commailto:e...@cloudscaling.com
wrote:
On Tue, Jul 23, 2013 at 4:41 PM, Logan McNaughton
lo...@bacoosta.commailto:lo...@bacoosta.com wrote:
I'm sure this has been asked before, but what exactly is the plan for Python 3
support?
31 matches
Mail list logo
