Possible major bug with zipimport on Windows in Python 3.3.4
Can someone please take a look at http://bugs.python.org/issue20621 for me? It appears that there is a significant problem with zipimport in 3.3.4. It's causing breakage in virtualenv but I've isolated the issue to what I think is Python itself. Basically, until this bug is fixed, virtualenv won't work on Windows with Python 3.3.4, as far as I can tell. Thanks, Paul
On Feb 13, 2014, at 3:53 PM, Paul Moore <p.f.moore@gmail.com> wrote:
Can someone please take a look at http://bugs.python.org/issue20621 for me? It appears that there is a significant problem with zipimport in 3.3.4. It's causing breakage in virtualenv but I've isolated the issue to what I think is Python itself.
Basically, until this bug is fixed, virtualenv won't work on Windows with Python 3.3.4, as far as I can tell.
Thanks, Paul _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/donald%40stufft.io
Does it affect 3.4? ----------------- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
On 13 February 2014 20:54, Donald Stufft <donald@stufft.io> wrote:
On Feb 13, 2014, at 3:53 PM, Paul Moore <p.f.moore@gmail.com> wrote:
Can someone please take a look at http://bugs.python.org/issue20621 for me? It appears that there is a significant problem with zipimport in 3.3.4. It's causing breakage in virtualenv but I've isolated the issue to what I think is Python itself.
Basically, until this bug is fixed, virtualenv won't work on Windows with Python 3.3.4, as far as I can tell.
Does it affect 3.4?
Just checked that. No, it's not an issue in 3.4rc0. Nor is it in 3.3.3, so it's a regression in the 3.3 series only. Paul
On 13 February 2014 20:58, Paul Moore <p.f.moore@gmail.com> wrote:
On 13 February 2014 20:54, Donald Stufft <donald@stufft.io> wrote:
On Feb 13, 2014, at 3:53 PM, Paul Moore <p.f.moore@gmail.com> wrote:
Can someone please take a look at http://bugs.python.org/issue20621 for me? It appears that there is a significant problem with zipimport in 3.3.4. It's causing breakage in virtualenv but I've isolated the issue to what I think is Python itself.
Basically, until this bug is fixed, virtualenv won't work on Windows with Python 3.3.4, as far as I can tell.
Does it affect 3.4?
Just checked that. No, it's not an issue in 3.4rc0. Nor is it in 3.3.3, so it's a regression in the 3.3 series only.
OK, this appears to be a serious regression that breaks virtualenv. Steve Dower suggested a workaround on the tracker, but I don't think that can be made to work in the case of virtualenv (for reasons not worth explaining now, ask me if you want the details though). Given where we are, what is the way forward here? I'm not entirely sure what I should be saying to the user who reported the bug in virtualenv. I think I'll recommend downgrading to 3.3.3 for now, but it would be good to be able to give an idea of what the longer term solution is likely to be. Thanks Paul
Am 15.02.2014 23:19, schrieb Paul Moore:
On 13 February 2014 20:58, Paul Moore <p.f.moore@gmail.com> wrote:
On 13 February 2014 20:54, Donald Stufft <donald@stufft.io> wrote:
On Feb 13, 2014, at 3:53 PM, Paul Moore <p.f.moore@gmail.com> wrote:
Can someone please take a look at http://bugs.python.org/issue20621 for me? It appears that there is a significant problem with zipimport in 3.3.4. It's causing breakage in virtualenv but I've isolated the issue to what I think is Python itself.
Basically, until this bug is fixed, virtualenv won't work on Windows with Python 3.3.4, as far as I can tell.
Does it affect 3.4?
Just checked that. No, it's not an issue in 3.4rc0. Nor is it in 3.3.3, so it's a regression in the 3.3 series only.
OK, this appears to be a serious regression that breaks virtualenv. Steve Dower suggested a workaround on the tracker, but I don't think that can be made to work in the case of virtualenv (for reasons not worth explaining now, ask me if you want the details though).
Given where we are, what is the way forward here? I'm not entirely sure what I should be saying to the user who reported the bug in virtualenv. I think I'll recommend downgrading to 3.3.3 for now, but it would be good to be able to give an idea of what the longer term solution is likely to be.
As soon as a patch has been provided and tested, I will make a schedule for 3.3.5 including the fix. Until then, using 3.3.3 is probably the best solution. Georg
On 16 February 2014 08:19, Georg Brandl <g.brandl@gmx.net> wrote:
As soon as a patch has been provided and tested, I will make a schedule for 3.3.5 including the fix. Until then, using 3.3.3 is probably the best solution.
Fantastic - thanks for that. Paul
16.02.14 10:19, Georg Brandl написав(ла):
As soon as a patch has been provided and tested, I will make a schedule for 3.3.5 including the fix. Until then, using 3.3.3 is probably the best solution.
Then could you please include the fix for #20538 (this bug allows easily crash Python e.g. by special HTTP request or e-mail). And I think it is very important to port the fix for #19619. Simple patch for #17671 fixes other crash (less important, because can be triggered only by programming error).
On 2/16/2014 2:52 PM, Serhiy Storchaka wrote:
16.02.14 10:19, Georg Brandl написав(ла):
As soon as a patch has been provided and tested, I will make a schedule for 3.3.5 including the fix. Until then, using 3.3.3 is probably the best solution.
Then could you please include the fix for #20538 (this bug allows easily crash Python e.g. by special HTTP request or e-mail). And I think it is very important to port the fix for #19619. Simple patch for #17671 fixes other crash (less important, because can be triggered only by programming error).
A 3.3.5 should have all the bugfixes committed before the candidate release. -- Terry Jan Reedy
Am 16.02.2014 21:14, schrieb Terry Reedy:
On 2/16/2014 2:52 PM, Serhiy Storchaka wrote:
16.02.14 10:19, Georg Brandl написав(ла):
As soon as a patch has been provided and tested, I will make a schedule for 3.3.5 including the fix. Until then, using 3.3.3 is probably the best solution.
Then could you please include the fix for #20538 (this bug allows easily crash Python e.g. by special HTTP request or e-mail). And I think it is very important to port the fix for #19619. Simple patch for #17671 fixes other crash (less important, because can be triggered only by programming error).
A 3.3.5 should have all the bugfixes committed before the candidate release.
Exactly. If these are all committed by the rc (only #19619 is missing AFAICT), they will go in. The 3.3.5 rc will be released next weekend, Feb 22th, and the final (if nothing else comes up) on Mar 1st. cheers, Georg
participants (5)
-
Donald Stufft -
Georg Brandl -
Paul Moore -
Serhiy Storchaka -
Terry Reedy