Someone over at StackOverflow has a problem with urlopen in Python 3.2.1:
http://stackoverflow.com/questions/6892573/problem-with-urlopen/6892843#6892...
This is the code:
from urllib.request import urlopen f = urlopen('http://online.wsj.com/mdc/public/page/2_3020-tips.html?mod=topnav_2_3000') page = f.read() f.close()
With Python 3.1 and Python 3.2.1 it works OK, but with Python 3.2.1 the read returns an empty string (I checked it myself).
In article 4E35DC94.2090208@mrabarnett.plus.com, MRAB python@mrabarnett.plus.com wrote:
Someone over at StackOverflow has a problem with urlopen in Python 3.2.1:
http://stackoverflow.com/questions/6892573/problem-with-urlopen/6892843#6892... 3
This is the code:
from urllib.request import urlopen f =
urlopen('http://online.wsj.com/mdc/public/page/2_3020-tips.html?mod=topnav_2_3 000') page = f.read() f.close()
With Python 3.1 and Python 3.2.1 it works OK, but with Python 3.2.1 the read returns an empty string (I checked it myself).
http://bugs.python.org/issue12576
With Python 3.1 and Python 3.2.1 it works OK, but with Python 3.2.1 the read returns an empty string (I checked it myself).
The bug is now fixed. Can you release a Python 3.2.2, maybe only with this fix?
Victor
On 8/8/2011 4:26 PM, Victor Stinner wrote:
With Python 3.1 and Python 3.2.1 it works OK, but with Python 3.2.1 the read returns an empty string (I checked it myself).
The bug is now fixed. Can you release a Python 3.2.2, maybe only with this fix?
Any new release should also have http://bugs.python.org/issue12540 which fixes another bad regression.
Am 09.08.2011 01:35, schrieb Terry Reedy:
On 8/8/2011 4:26 PM, Victor Stinner wrote:
With Python 3.1 and Python 3.2.1 it works OK, but with Python 3.2.1 the read returns an empty string (I checked it myself).
The bug is now fixed. Can you release a Python 3.2.2, maybe only with this fix?
Any new release should also have http://bugs.python.org/issue12540 which fixes another bad regression.
I can certainly release a version with these two fixes. Question is, should we call it 3.2.2, or 3.2.1.1 (3.2.1p1)?
Georg
On 8/9/2011 2:02 AM, Georg Brandl wrote:
Am 09.08.2011 01:35, schrieb Terry Reedy:
On 8/8/2011 4:26 PM, Victor Stinner wrote:
With Python 3.1 and Python 3.2.1 it works OK, but with Python 3.2.1 the read returns an empty string (I checked it myself).
The bug is now fixed. Can you release a Python 3.2.2, maybe only with this fix?
Any new release should also have http://bugs.python.org/issue12540 which fixes another bad regression.
I can certainly release a version with these two fixes. Question is, should we call it 3.2.2, or 3.2.1.1 (3.2.1p1)?
I believe precedent and practicality say 3.2.2. How much more, if anything is up to you. The important question is whether Martin is willing to do a Windows installer, as 12540 only affects Windows.
2011-08-09 08:02:45 Georg Brandl napisał(a):
Am 09.08.2011 01:35, schrieb Terry Reedy:
On 8/8/2011 4:26 PM, Victor Stinner wrote:
With Python 3.1 and Python 3.2.1 it works OK, but with Python 3.2.1 the read returns an empty string (I checked it myself).
The bug is now fixed. Can you release a Python 3.2.2, maybe only with this fix?
Any new release should also have http://bugs.python.org/issue12540 which fixes another bad regression.
I can certainly release a version with these two fixes. Question is, should we call it 3.2.2, or 3.2.1.1 (3.2.1p1)?
I would suggest that a normal release with all changes committed on 3.2 branch be created.
Am 09.08.2011 16:25, schrieb Barry Warsaw:
On Aug 09, 2011, at 08:02 AM, Georg Brandl wrote:
I can certainly release a version with these two fixes. Question is, should we call it 3.2.2, or 3.2.1.1 (3.2.1p1)?
Definitely 3.2.2.
OK, 3.2.2 it is. I will have to have a closer look at the other changes in the branch to decide if it'll be a single(double)-fix only release.
Schedule would be roughly as follows: rc1 this Friday/Saturday, then I'm on vacation for a little more than one week, so final would be the weekend of 27/28 August.
Georg