Changes by STINNER Victor [EMAIL PROTECTED]:
Removed file: http://bugs.python.org/file10860/_multiprocessing_connection.patch
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3321
___
Justin Harper [EMAIL PROTECTED] added the comment:
Further research reveals that the problem appears to be with the
gtk.Assistant class in PyGTK 2.10, not the subprocess lib.
Report can be closed.
___
Python tracker [EMAIL PROTECTED]
Changes by Raymond Hettinger [EMAIL PROTECTED]:
--
assignee: - rhettinger
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3106
___
___
Python-bugs-list
Benjamin Peterson [EMAIL PROTECTED] added the comment:
Well, booleans technically are integers.
--
nosy: +benjamin.peterson
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3354
___
Changes by Benjamin Peterson [EMAIL PROTECTED]:
--
resolution: - invalid
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3335
___
Changes by Benjamin Peterson [EMAIL PROTECTED]:
--
resolution: - wont fix
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3354
___
Nick Edds [EMAIL PROTECTED] added the comment:
Yeah that import_as_names definitely shouldn't be there. I don't know
what I was thinking at the time, but that should just be an any I
believe. I'll clean this up today or tomorrow, update fix_imports2 as
well, and try to fix the tests for
Benjamin Peterson [EMAIL PROTECTED] added the comment:
done in r64947.
--
resolution: - fixed
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2512
___
Christoph Zwerschke [EMAIL PROTECTED] added the comment:
The problem is not only that the error message TypeError: an integer is
required has integer instead of boolean, but it does not mention
the attribute name reverse, i.e. it does not even say *where* the
integer is required. I firmly
Benjamin Peterson [EMAIL PROTECTED] added the comment:
Patches are welcome.
--
priority: - low
resolution: wont fix -
status: closed - open
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3354
Changes by Andrii V. Mishkovskyi [EMAIL PROTECTED]:
--
nosy: +mishok13
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3354
___
___
Python-bugs-list
New submission from Antoine Pitrou [EMAIL PROTECTED]:
With the latest py3k, some tests fail when run in debug mode:
- test_distutils fails with the following message:
FAILED (errors=1)
Traceback (most recent call last):
File Lib/test/test_distutils.py, line 17, in module
test_main()
File
Raymond Hettinger [EMAIL PROTECTED] added the comment:
I think this is closer to a language wide change and should probably be
addressed for 2.7 and 3.1. It would be great to change the C argument
parsing API to make its error messages more specific.
For Py2.6, I think things are fine as it
Ralf Schmitt [EMAIL PROTECTED] added the comment:
this patch adds a digest_update function.
digest_update calls EVP_DigestUpdate(..) with chunks of 16 MB size and
also checks for signals.
I didn't write any tests (as they will most probably annoy many people
cause they would need much memory).
Nick Coghlan [EMAIL PROTECTED] added the comment:
At this stage I'm still inclined to skip the warnings completely - at
the very least, any eventual removals will go through a full deprecation
cycle in 2.7/3.1 before being removed in 2.8/3.2.
It's also much easier to be sure we aren't adversely
Benjamin Peterson [EMAIL PROTECTED] added the comment:
Neither of these fail for me on MacOS.
--
nosy: +benjamin.peterson
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3356
___
Antoine Pitrou [EMAIL PROTECTED] added the comment:
On another machine, with another distro (Debian stable) and another gcc
version (4.1.2 instead of 4.3.1), I even get a segmentation fault on
test_distutils:
$ ./python Lib/test/test_set.py
test_add (__main__.TestSet) ... ok
test_and
New submission from Chester [EMAIL PROTECTED]:
This relates to Python 3.x. Do this please:
import sys; print(sys.__doc__)
Please fix the following line of text in that __doc__ file of the sys
module:
stdin -- standard input file object; used by raw_input() and input()
This line of text should
Christoph Zwerschke [EMAIL PROTECTED] added the comment:
Agree. Seems to be a more general weakness of the argument parsing of
builtin functions and methods, that calls for a general solution instead
of a local patch. Luckily there are not so many cases where the errors
are misleading, since the
Benjamin Peterson [EMAIL PROTECTED] added the comment:
Thanks. Fixed in r64956.
--
nosy: +benjamin.peterson
resolution: - fixed
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3357
Raymond Hettinger [EMAIL PROTECTED] added the comment:
The patch looks good. I would coded hex_from_char() using a lookup
into 0123456789abcdef which uses no unpredicatable branches.
Likewise, I would done hex_from_char() with a case statement (limiting
the call to single unpredicatable
New submission from Nick Edds [EMAIL PROTECTED]:
Here is an iterative replacement to _recursive_matches for Wildcard
Patterns. It's not really much faster now, although I think there is
some room to improve it. It's doesn't seem like the most elegant
solution, but it works. It passes all of the
New submission from anatoly techtonik [EMAIL PROTECTED]:
'rU' universal newline support is useless, because read lines end with
'\n' regardless of actual line end in the source file. Applications that
care about line ends still open file in binary mode and gather the stats
manually.
So, to
101 - 123 of 123 matches
Mail list logo