New submission from flox :
In the Python «Unicode HOWTO», we still read the statement:
«For example, Python's default encoding is the 'ascii'
encoding.»
Here:
http://svn.python.org/view/python/branches/py3k/Doc/howto/unicode.rst?revision=72294&view=markup
--
ass
New submission from flox :
Found 2 typos:
- Uniode instead of Unicode
- Acknowledgements instead of Acknowledgments
And the following reference is broken (Jason Orendorff website):
http://www.jorendorff.com/articles/unicode/
The last version is dated 2007 on the wayback machine:
http
New submission from flox :
Running on Debian Lenny, with Python 3.1.
The Python 2.5 version is OK.
~ $ python3 --version
Python 3.1.1+
~ $ python3 -m doctest
F..
==
FAIL: Doctest: __main__.DebugRunner
New submission from flox :
The last code snippet on section "25.2.3.2 How are Docstring Examples
Recognized?" does not output the expected result.
http://docs.python.org/dev/py3k/library/doctest.html#how-are-docstring-examples-recognized
Documentation example:
>&g
New submission from flox :
Yes, you can reduce the fraction 1234/5678.
Bad Luck :p
~ $ python3 -m doctest /usr/lib/python3.1/fractions.py
**
File "/usr/lib/python3.1/fractions.py", li
New submission from flox :
I've tried some experiments with module uuid, and I meet some
inconsistencies between the documentation, the docstring and the real
behavior of the module.
An interactive session is worth a thousand words:
>>> import uuid
>>> uuid.UUID(byt
flox added the comment:
Attached patch gives coherence:
* both UUID.bytes and UUID.bytes_le return a "bytes" object
* the random tests are explicitly skipped
Then the documentation needs fixing, too.
--
keywords: +patch
Added file: http://bugs.python.org
New submission from flox :
I've tested the docstring of the module subprocess.
Python 2.5 is OK, but Python 3.1 fails.
~ $ python2.5 -m doctest /usr/lib/python2.5/subprocess.py
...
--
Ran 15 tests in 0.012
flox added the comment:
I fixed the docstring inconsistency (see patch) and some obvious things.
But I still have errors.
~ $ python3 -m doctest py3_failed/subprocess.py
**
File "py3_failed/subprocess.py", li
flox added the comment:
It may be fixed with "# doctest: +ELLIPSIS" and "# doctest: +SKIP"
directives...
But it is probably platform-dependent.
I have tested only with Debian Lenny.
--
___
Python tracker
<http://bu
flox added the comment:
I am ok with the proposal of removing the current "selftest" default
behavior.
And thank you for the tip.
I tried the command "python -m doctest Lib/*.py" and I found interesting
things:
* #7379 about Lib/fractions.py
* #7380 about Lib/uuid.p
flox added the comment:
Forget the "python2.5 -m doctest /usr/lib/python2.5/subprocess.py" in
first message msg95625.
This command does not do what I guessed. And there's no doctest in the
Python2.5 "subprocess" module.
The attached patch may be enough to fix the
flox added the comment:
Patch with documentation included. (branches/py3k)
--
assignee: -> georg.brandl
components: +Documentation
nosy: +georg.brandl
Added file: http://bugs.python.org/file15388/issue7380.diff
___
Python tracker
&l
Changes by flox :
Removed file: http://bugs.python.org/file15385/issue7380_uuid.diff
___
Python tracker
<http://bugs.python.org/issue7380>
___
___
Python-bugs-list mailin
flox added the comment:
Patch proposed.
--
Added file: http://bugs.python.org/file15391/issue7376_usage.diff
___
Python tracker
<http://bugs.python.org/issue7
Changes by flox :
Removed file: http://bugs.python.org/file15391/issue7376_usage.diff
___
Python tracker
<http://bugs.python.org/issue7376>
___
___
Python-bugs-list mailin
Changes by flox :
Added file: http://bugs.python.org/file15392/issue7376_usage.diff
___
Python tracker
<http://bugs.python.org/issue7376>
___
___
Python-bugs-list mailin
flox added the comment:
Patch could be applied to Python 2.6 and trunk too.
--
versions: +Python 2.6, Python 2.7
___
Python tracker
<http://bugs.python.org/issue7
flox added the comment:
The relevant documentation for Python 2.6 is there.
http://docs.python.org/reference/datamodel.html#new-style-and-classic-classes
The PEP 3115 is implemented for Python >= 3.0.
There's nothing wrong.
--
nos
flox added the comment:
I would think to use weak references in order to prevent such leaks.
With the patch attached, if the handler is not referenced anywhere, it
is closed.
However named handlers are not closed (because of hard reference in
_handlers dictionary).
--
nosy: +flox
Changes by flox :
Removed file: http://bugs.python.org/file15395/issue6615_weakref.diff
___
Python tracker
<http://bugs.python.org/issue6615>
___
___
Python-bugs-list m
flox added the comment:
yep... patch was not clean. Sorry :(
I changed it.
It passes the 21 tests of the test_logging suite.
And the count of references decreases with the test:
>>> import logging
>>> handler = logging.Handler()
>>> handler = logging.Handler()
flox added the comment:
Updated the patch with technical recommendations from Antoine.
I kept the _handlerList as a list because "It allows handlers to be
removed in reverse of order initialized."
And some tests are needed to outline the change.
--
Added file: http://bugs.
Changes by flox :
Removed file: http://bugs.python.org/file15396/issue6615_weakref.diff
___
Python tracker
<http://bugs.python.org/issue6615>
___
___
Python-bugs-list m
flox added the comment:
Small change to acquire the module lock before working on _handlerList.
--
Added file: http://bugs.python.org/file15398/issue6615_weakref.diff
___
Python tracker
<http://bugs.python.org/issue6
Changes by flox :
Removed file: http://bugs.python.org/file15397/issue6615_weakref.diff
___
Python tracker
<http://bugs.python.org/issue6615>
___
___
Python-bugs-list m
flox added the comment:
Thank you Vinay.
Since you "reversed()" the _handlerList, the following part need to be
changed:
Index: Lib/logging/__init__.py
===
--- Lib/logging/__init__.py (revision 76508)
+++ Lib/loggin
flox added the comment:
It looks similar to issue7378, but the latter has more details.
Close as duplicate?
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue4
flox added the comment:
Please close as invalid.
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue4158>
___
___
Python-bugs-list mailing list
Unsub
Changes by flox :
--
nosy: -flox
___
Python tracker
<http://bugs.python.org/issue4158>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.pyth
flox added the comment:
This issue is somewhat related to the same issue with pickle.
See issue1398 for the explanation.
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue4
flox added the comment:
I experienced same failure (trunk is OK).
It seems that r70531 needs backporting.
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue7
flox added the comment:
Tested on debian with r76600 (/branches/release26-maint
No error.
~/dev/python/release26-maint $ ./python Lib/test/regrtest.py -uall
test_urllib2 test_pydoc
test_urllib2
test_pydoc
All 2 tests OK.
~/dev/python/release26-maint $
Is it specific to Windows
flox added the comment:
Proposed patch following suggestion of And Clover.
Compliant with documentation:
«Files are always opened in binary mode, even if no binary mode was
specified. This is done to avoid data loss due to encodings using 8-bit
values. This means that no automatic conversion
Changes by flox :
Added file: http://bugs.python.org/file15423/issue691291_py3k.diff
___
Python tracker
<http://bugs.python.org/issue691291>
___
___
Python-bugs-list m
Changes by flox :
Added file: http://bugs.python.org/file15426/issue7380_py3k.diff
___
Python tracker
<http://bugs.python.org/issue7380>
___
___
Python-bugs-list mailin
Changes by flox :
Removed file: http://bugs.python.org/file15388/issue7380.diff
___
Python tracker
<http://bugs.python.org/issue7380>
___
___
Python-bugs-list mailin
flox added the comment:
Proposed docstring patch.
--
keywords: +patch
nosy: +flox
versions: +Python 3.2
Added file: http://bugs.python.org/file15428/issue7417_py3k.diff
___
Python tracker
<http://bugs.python.org/issue7
flox added the comment:
I guess you missed the quotes.
$ ./python foo.py
Traceback (most recent call last):
File "foo.py", line 2, in
from hashlib import *
TypeError: attribute name must be string, not 'tuple'
--
nosy: +flox
__
flox added the comment:
Indentation is not easy on this part.
The list of arguments overflow the 79 chars limit.
With the proposed patch, the generated output is something like:
open(file, mode='r', buffering=None, encoding=None,
errors=None, newline=None, closefd=Tru
flox added the comment:
According to PEP257:
«Multi-line docstrings consist of a summary line just like a one-line
docstring, followed by a blank line, followed by a more elaborate
description.»
Maybe this second patch is more conventional?
--
Added file: http://bugs.python.org
Changes by flox :
Added file: http://bugs.python.org/file15435/issue691291.diff
___
Python tracker
<http://bugs.python.org/issue691291>
___
___
Python-bugs-list mailin
Changes by flox :
Removed file: http://bugs.python.org/file15422/issue691291.diff
___
Python tracker
<http://bugs.python.org/issue691291>
___
___
Python-bugs-list mailin
Changes by flox :
Removed file: http://bugs.python.org/file15434/issue7417_py3k_pep257.diff
___
Python tracker
<http://bugs.python.org/issue7417>
___
___
Python-bug
Changes by flox :
Removed file: http://bugs.python.org/file15428/issue7417_py3k.diff
___
Python tracker
<http://bugs.python.org/issue7417>
___
___
Python-bugs-list mailin
flox added the comment:
Actually the docstring of _pyio.open Python function should not change.
The patch is smaller.
--
Added file: http://bugs.python.org/file15436/issue7417_py3k.diff
___
Python tracker
<http://bugs.python.org/issue7
flox added the comment:
Ulrik,
I agree that most builtins have the signature on first lines.
I will not apply this part of the PEP257.
But it seems that the "[...]" syntax is not enforced for all builtins.
See "help(print)", "help(sorted)" and "help(__im
Changes by flox :
Removed file: http://bugs.python.org/file15436/issue7417_py3k.diff
___
Python tracker
<http://bugs.python.org/issue7417>
___
___
Python-bugs-list mailin
flox added the comment:
Or I suggest something more verbose...
>>> print(open.__doc__)
open(filename) -> file object for reading in text mode
open(filename, mode=binary[, buffering]) -> file object in binary mode
open(filename[, mode=text][, buffering][,encoding][,e
flox added the comment:
(patch attached: explicit signature)
I vote +1 for something more explicit.
« Explicit is better than implicit. »
>>> help(open)
Help on built-in function open in module io:
open(...)
open(file_name_or_path) -> file object for reading in text m
Changes by flox :
Added file: http://bugs.python.org/file15442/issue7417_py3k_explicit.diff
___
Python tracker
<http://bugs.python.org/issue7417>
___
___
Python-bug
Changes by flox :
Removed file: http://bugs.python.org/file15441/issue7417_py3k_explicit.diff
___
Python tracker
<http://bugs.python.org/issue7417>
___
___
Python-bug
Changes by flox :
Removed file: http://bugs.python.org/file15386/issue7381_first.diff
___
Python tracker
<http://bugs.python.org/issue7381>
___
___
Python-bugs-list mailin
flox added the comment:
Patch against the trunk, and against the Py3k branch.
It fixes:
* docstring and documentation formatting
* and examples
--
assignee: -> georg.brandl
components: +Documentation
nosy: +georg.brandl
versions: +Python 2.6, Python 2.7
Added file: h
Changes by flox :
Added file: http://bugs.python.org/file15447/issue7381_py3k.diff
___
Python tracker
<http://bugs.python.org/issue7381>
___
___
Python-bugs-list mailin
flox added the comment:
It seems fixed on trunk.
It is fixed on Python 3.1 and 3.2, too.
With Python 2.6 I see the error:
>>> ./python partial_bug.py
TypeError: can't pickle partial objects
Documentation for "trunk" and "py3k&qu
flox added the comment:
Already fixed on Python trunk (2.7).
Fixed on branches 3.1 and 3.2, too.
--
___
Python tracker
<http://bugs.python.org/issue4380>
___
___
flox added the comment:
Actually it should use the TESTFN filename which is always writable.
Patch attached.
--
keywords: +patch
nosy: +flox
Added file: http://bugs.python.org/file15448/issue7431.diff
___
Python tracker
<http://bugs.python.
Changes by flox :
--
versions: +Python 3.2
___
Python tracker
<http://bugs.python.org/issue7431>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from flox :
In python 3.x there's a single type for integer: int.
The automatic conversion of the test suite has created many tests which
are duplicate of each other.
The attached patch removes duplication of tests, and fix the strings for
these modules:
Lib/random.py
Changes by flox :
--
keywords: +patch
Added file: http://bugs.python.org/file15449/issue7435_py3k.diff
___
Python tracker
<http://bugs.python.org/issue7
flox added the comment:
there's a patch proposed to add cp65001 alias: issue6058
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue7441>
___
___
Changes by flox :
--
versions: +Python 2.6, Python 3.1, Python 3.2
___
Python tracker
<http://bugs.python.org/issue6058>
___
___
Python-bugs-list mailin
Changes by flox :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue6472>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/m
flox added the comment:
There's many differences between both implementations.
I don't know if we can live with them or not.
~ $ ./python
Python 3.1.1+ (release31-maint:76650, Dec 3 2009, 17:14:50)
[GCC 4.3.2] on linux2
Type "help", "copyright", "credits
flox added the comment:
Proposed patch fixes most of the discrepancies between both implementations.
It restores some features that were lost with Python 3:
* cElement slicing and extended slicing
* iterparse, cET.getiterator and cET.findall return an iterator
(as documented)
Some tests
Changes by flox :
Added file: http://bugs.python.org/file15462/issue6472_py3k.diff
___
Python tracker
<http://bugs.python.org/issue6472>
___
___
Python-bugs-list mailin
flox added the comment:
I fixed it differently, using the upstream modules (Thank you Fredrik).
* ElementTree 1.3a3-20070912
* cElementTree 1.0.6-20090110
It works.
And it closes issue1143, too.
--
Added file: http://bugs.python.org/file15468/issue6472_upstream.diff
Changes by flox :
--
versions: -Python 3.0
Added file: http://bugs.python.org/file15469/issue6472_upstream_py3k.diff
___
Python tracker
<http://bugs.python.org/issue6
Changes by flox :
Removed file: http://bugs.python.org/file15462/issue6472_py3k.diff
___
Python tracker
<http://bugs.python.org/issue6472>
___
___
Python-bugs-list mailin
Changes by flox :
Removed file: http://bugs.python.org/file15461/issue6472.diff
___
Python tracker
<http://bugs.python.org/issue6472>
___
___
Python-bugs-list mailin
flox added the comment:
Patch proposed with latest versions:
* ElementTree 1.3a3-20070912
* cElementTree 1.0.6-20090110
Attached to issue6472.
--
keywords: +patch
nosy: +flox
Added file: http://bugs.python.org/file15470/issue1143_ET13_cET106.diff
Changes by flox :
Removed file: http://bugs.python.org/file15470/issue1143_ET13_cET106.diff
___
Python tracker
<http://bugs.python.org/issue1143>
___
___
Python-bug
flox added the comment:
I see some new features in the changelog.
I will try to update the documentation during the week.
(patch "py3k" fixed: support assignment of arbitrary sequences)
--
Added file: http://bugs.python.org/file15471/issue6472_upstream
Changes by flox :
Removed file: http://bugs.python.org/file15469/issue6472_upstream_py3k.diff
___
Python tracker
<http://bugs.python.org/issue6472>
___
___
Python-bug
flox added the comment:
test_textwrap seems OK with r76697
I still have leaks on test_pipes and test_urllib:
~ $ ./python Lib/test/regrtest.py -R : test_textwrap \
test_pipes test_urllib
test_pipes leaked [0, -26, 0, 26] references, sum=0
test_pipes leaked [0, -26, 26, -26
Changes by flox :
Added file: http://bugs.python.org/file15479/issue5596_urllib_py3k.diff
___
Python tracker
<http://bugs.python.org/issue5596>
___
___
Python-bugs-list m
Changes by flox :
Added file: http://bugs.python.org/file15480/issue5596_pipes_py3k.diff
___
Python tracker
<http://bugs.python.org/issue5596>
___
___
Python-bugs-list m
flox added the comment:
Patch for the test refleaks:
* test_pipes
* test_urllib
--
___
Python tracker
<http://bugs.python.org/issue5596>
___
___
Python-bug
flox added the comment:
And the test_urllib may leak on 2.7, too.
Patch attached.
--
Added file: http://bugs.python.org/file15482/issue5596_urllib.diff
___
Python tracker
<http://bugs.python.org/issue5
Changes by flox :
--
versions: +Python 2.7
___
Python tracker
<http://bugs.python.org/issue5596>
___
___
Python-bugs-list mailing list
Unsubscribe:
flox added the comment:
Another false-positive in test_zipimport_support.
Both on 2.7 and 3.2.
Patch attached.
--
Added file: http://bugs.python.org/file15485/issue5596_zipimport_support.diff
___
Python tracker
<http://bugs.python.org/issue5
Changes by flox :
Added file:
http://bugs.python.org/file15486/issue5596_zipimport_support_py3k.diff
___
Python tracker
<http://bugs.python.org/issue5596>
___
___
Pytho
flox added the comment:
This bug does not occur on Debian 64 bits.
~ $ uname -srvm
Linux 2.6.30-bpo.1-amd64 #1 SMP Mon Aug 17 08:42:50 UTC 2009 x86_64
Tested with variants:
from random import getrandbits
self.checkequal(-1, 'ab', 'find', '
flox added the comment:
I got it to crash (2.7):
~ $ ./python Lib/test/regrtest.py string_tests test_unicode test_str
test_unicode
test test_unicode failed -- Traceback (most recent call last):
AssertionError: -1 != -8276732
test_str
test test_str failed -- Traceback (most recent call last
flox added the comment:
I reviewed the patch, and it seems partially redundant.
Actually the "find" method was not broken.
There is already a test "if (str_len < 0) return -1;" for this one.
See attached patch.
--
Added file: http://bugs.python.org/file155
New submission from flox :
While looking at issue7458 I stopped on:
/* XXX - create reversefastsearch helper! */
Here is the patch which is just the translation of the same algorithm
already implemented for "find/index".
http://effbot.org/zone/stringlib.htm
Note: it supersedes
flox added the comment:
(removed comment which should not be copied)
--
Added file: http://bugs.python.org/file15507/fastsearch_rfind.patch
___
Python tracker
<http://bugs.python.org/issue7
Changes by flox :
Removed file: http://bugs.python.org/file15505/fastsearch_rfind.patch
___
Python tracker
<http://bugs.python.org/issue7462>
___
___
Python-bugs-list m
flox added the comment:
Patch for the documentation. (source: upstream documentation)
--
Added file: http://bugs.python.org/file15513/issue6472_upstream_docs.diff
___
Python tracker
<http://bugs.python.org/issue6
flox added the comment:
Yes, confirmed too. Both 3.1 and 3.2 are broken.
Minimal sequence to trigger the bug:
"""
~ $ ./python
Python 3.2a0 (py3k:76743M, Dec 10 2009, 12:19:41)
[GCC 4.3.2] on linux2
Type "help", "copyright", "credits" or "li
flox added the comment:
Fix is coming soon...
## Sample code:
import gc
tuple(gc.collect() for i in range(11))
## python: Objects/tupleobject.c:853: _PyTuple_Resize:
## Assertion `g->gc.gc_refs != (-2)' failed.
And Trunk is affected
--
versions: +Py
flox added the comment:
Well... here comes the patch.
--
keywords: +patch
Added file: http://bugs.python.org/file15520/issue7466.diff
___
Python tracker
<http://bugs.python.org/issue7
Changes by flox :
Removed file: http://bugs.python.org/file15520/issue7466.diff
___
Python tracker
<http://bugs.python.org/issue7466>
___
___
Python-bugs-list mailin
Changes by flox :
Added file: http://bugs.python.org/file15521/issue7466.diff
___
Python tracker
<http://bugs.python.org/issue7466>
___
___
Python-bugs-list mailin
New submission from flox :
AFAIK these codecs were not ported to Python 3.
1. I found no hint in documentation on this matter.
2. Is it possible to contribute some of them, or there's a good reason
to look elsewhere?
--
components: Library (Lib)
messages: 96218
nosy: flox
sev
flox added the comment:
«Everything you thought you knew about binary data and Unicode
has changed.»
Reopening for the documentation part.
This "mistake" deserves some words in the documentation:
docs.python.org/dev/py3k/whatsnew/3.0.html
#text-vs-data-instead-of-unicod
flox added the comment:
Is it possible to add "DeprecationWarning" for these codecs
when using "python -3" ?
>>> {}.has_key('a')
__main__:1: DeprecationWarning: dict.has_key() not supported in 3.x;
use the in operator
False
>>> print
Changes by flox :
--
versions: +Python 2.7
___
Python tracker
<http://bugs.python.org/issue7475>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by flox :
--
title: No hint about codecs removed : base64 bz2 hex zlib ... -> No hint about
codecs removed: base64 bz2 hex zlib ...
___
Python tracker
<http://bugs.python.org/iss
1 - 100 of 162 matches
Mail list logo
