New submission from Ryan Leslie :
py> StringIO.StringIO("foo").read(long(1))
'f'
py> io.BytesIO("foo").read(long(1))
Traceback (most recent call last):
File "", line 1, in
TypeError: integer argument expected, got 'long'
This is know
Ryan Leslie added the comment:
Yes, I think this fix should have been included in the 2.6 branch. I
subscribed Amaury to look into that when I last updated.
--
___
Python tracker
<http://bugs.python.org/issue7
Ryan Leslie added the comment:
I expect this should already be fixed by the commit in
http://bugs.python.org/issue6511
BadZipFile will now be raised for empty files rather than IOError, and
so ZipFile._GetContents() should now also close the file.
The fix was committed to trunk, but I don
New submission from Ryan Leslie :
http://docs.python.org/download.html shows this:
Download Python 2.6.4c1 Documentation
We don't package the documentation for development releases for
download. Downloads will be available for the final release.
This is not really acceptabl
Ryan Leslie added the comment:
Looks like a merge has gone bad. NullHandler has existed for a while on
trunk but is not present in the 2.6.3 tag (__all__ was updated to
include it, however):
/python/tags/r263/Lib/logging/__init__.py
--
nosy: +ryles
Ryan Leslie added the comment:
Hi Art,
Thanks for working on this. I've taken a look at the patch.
The fix to read_test looks correct. Of course, I would consider a more
descriptive variable name than 'b'.
The changes to read() are an improvement, but I think we need to be
New submission from Ryan Leslie :
The zipfile.ZipFile.open() behavior with mode 'U' or 'rU' is not quite
as advertised in
http://docs.python.org/library/zipfile.html#zipfile.ZipFile.open
Here is an example:
$ echo -ne "This is an example\r\nWhich demonstrates a pro
Changes by Ryan Leslie :
--
nosy: +jnoller
___
Python tracker
<http://bugs.python.org/issue6362>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Ryan Leslie :
While developing an application, an inconsistency was noted where,
depending on the particular signal handler in use,
multiprocessing.Queue.put() may (or may not) raise OSError() after
sys.exit() was called by the handler. The following example, which was
tested
Changes by Ryan Leslie :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue6082>
___
___
Python-bugs-list mailing list
Unsubscri
Ryan Leslie added the comment:
Thanks for the quick response, Philip. Makes even more sense now that I see:
Python 2.6.1 (r261:67515, Apr 2 2009, 18:25:55)
[GCC 4.1.2 20071124 (Red Hat 4.1.2-42)] on linux2
Type "help", "copyright", "credits" or "license&qu
New submission from Ryan Leslie :
Python 2.6.1 (r261:67515, Apr 2 2009, 18:25:55)
[GCC 4.1.2 20071124 (Red Hat 4.1.2-42)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys, os
>>> os.path.
Ryan Leslie added the comment:
Yeah, storing pickled queues in the file system makes for some easy IPC
:) It wasn't a very original idea, I took the pickling comments in the
documentation at face value:
http://docs.python.org/library/multiprocessing.html#proxy-objects
So, from what I can
New submission from Ryan Leslie :
Terminal 1:
Python 2.6.1 (r261:67515, Apr 2 2009, 18:25:55)
[GCC 4.1.2 20071124 (Red Hat 4.1.2-42)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from multiprocessing.mana
New submission from Ryan Leslie :
e.g.
>>> from datetime import datetime
>>>
>>> datetime.strptime("19951001", "%Y%m%d")
datetime.datetime(1995, 10, 1, 0, 0)
>>>
>>> datetime.strptime("19951000", "%Y%m%d") # da
New submission from Ryan Leslie :
When using the logging package, if a StreamHandler is configured with
stderr and stderr is redirected to a pipe which no longer has readers,
then StreamHandler.emit() will result in an IOError for "Broken pipe".
The exception will be
16 matches
Mail list logo