On Fri, Mar 30, 2012 at 12:07 PM, Éric Araujo wrote:
> Le 29/03/2012 22:04, Nick Coghlan a écrit :
>> On Fri, Mar 30, 2012 at 4:26 AM, Carl Meyer wrote:
>>> I've added this option as a comment on bug 1. The title of that bug
>>> is worded such that it could be reasonably resolved either with
Le 29/03/2012 22:04, Nick Coghlan a écrit :
> On Fri, Mar 30, 2012 at 4:26 AM, Carl Meyer wrote:
>> I've added this option as a comment on bug 1. The title of that bug
>> is worded such that it could be reasonably resolved either with the
>> backwards-compatibility fix or the release notes add
On Fri, Mar 30, 2012 at 4:26 AM, Carl Meyer wrote:
> I've added this option as a comment on bug 1. The title of that bug
> is worded such that it could be reasonably resolved either with the
> backwards-compatibility fix or the release notes addition, the release
> managers can decide what see
On 03/29/2012 11:39 AM, David Malcolm wrote:
>> jaraco@vdm-dev:~$ env/bin/python -c "import os; os.urandom()"
>> Traceback (most recent call last):
>> File "", line 1, in
>> AttributeError: 'module' object has no attribute 'urandom'
>
> It looks like this a symptom of the move of urandom to os.
On Wed, 2012-03-28 at 18:22 +, Jason R. Coombs wrote:
> I see this was reported as a debian bug.
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665776
>
> To reproduce, using virtualenv 1.7+ on Python 2.7.2 on Ubuntu, create
> a virtualenv. Move that virtualenv to a host with Python 2.7.3R
Thanks Jason for raising this. I just assumed that this was virtualenv's
fault (which it is) and didn't consider raising it here, but a note in
the release notes for the affected Python versions will certainly reach
many more of the likely-to-be-affected users.
FTR, I confirmed that the issue also
On Thu, 29 Mar 2012 11:41:46 -, "Jason R. Coombs" wrote:
> Does the issue only exist for Python 2.6 and 2.7?
It might exist for 3.1 and 3.2 as well.
> I'm not familiar with the release process. What's the next step?
I would suggest opening an issue on the tracker and marking it as a
release
Carl,
I've drafted some notes: http://piratepad.net/PAZ3CEq9CZ
Please feel free to edit them. If you want to chat, I can often be reached
on freenode as 'jaraco' or XMPP at my e-mail address if you want to sprint
on this in real-time.
Does the issue only exist for Python 2.6 and 2.7?
I'm not fa
On Wed, 28 Mar 2012 20:56:30 -, "Jason R. Coombs" wrote:
> Will the release notes include something about this change, since it will
> likely have broad backward incompatibility for all existing virtualenvs? I
> wouldn't expect someone in operations to read the virtualenv news to find
> out wh
> -Original Message-
> From: python-dev-bounces+jaraco=jaraco@python.org [mailto:python-
> dev-bounces+jaraco=jaraco@python.org] On Behalf Of Carl Meyer
> Sent: Wednesday, 28 March, 2012 14:48
>
> The workaround is easy: just re-run virtualenv on that path with the new
> interprete
Hi Jason,
On 03/28/2012 12:22 PM, Jason R. Coombs wrote:
> To reproduce, using virtualenv 1.7+ on Python 2.7.2 on Ubuntu, create a
> virtualenv. Move that virtualenv to a host with Python 2.7.3RC2 yields:
>
> jaraco@vdm-dev:~$ /usr/bin/python2.7 -V
>
> Python 2.7.3rc2
>
> jaraco@vdm-dev:~$ env/
I see this was reported as a debian bug.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665776
We encountered it as well.
To reproduce, using virtualenv 1.7+ on Python 2.7.2 on Ubuntu, create a
virtualenv. Move that virtualenv to a host with Python 2.7.3RC2 yields:
jaraco@vdm-dev:~$ /
12 matches
Mail list logo
