flox added the comment:
On 3.1, 3.2 same issue:
>>> pickle.loads(b'0')
Segmentation fault
------
nosy: +flox
versions: +Python 2.7, Python 3.1, Python 3.2
___
Python tracker
<http://bug
Changes by flox :
Added file: http://bugs.python.org/file15594/doc_faq_design_py3k.diff
___
Python tracker
<http://bugs.python.org/issue7493>
___
___
Python-bugs-list m
flox added the comment:
Updated patch with suggestions of Ezio.
--
title: doc: patch for py3k/Doc/faq/design.rst -> doc: patch for
Doc/faq/design.rst
versions: +Python 2.6, Python 2.7
Added file: http://bugs.python.org/file15593/doc_faq_design.d
Changes by flox :
Removed file: http://bugs.python.org/file15542/py3k_doc_faq_design.diff
___
Python tracker
<http://bugs.python.org/issue7493>
___
___
Python-bugs-list m
Changes by flox :
Added file: http://bugs.python.org/file15591/issue7537_tolerant_stdout.diff
___
Python tracker
<http://bugs.python.org/issue7537>
___
___
Python-bug
Changes by flox :
Removed file: http://bugs.python.org/file15590/issue7537_tolerant_stdout.diff
___
Python tracker
<http://bugs.python.org/issue7537>
___
___
Python-bug
flox added the comment:
Maybe the "sys.stdout.write" method can be wrapped in a decorator or a
context manager?
See example of decorator attached.
--
keywords: +patch
nosy: +flox
Added file: http://bugs.python.org/file15590/issue7537_tolerant_s
flox added the comment:
I proposed a patch which solve this issue and improve performance of
str.rfind. See issue 7462.
--
___
Python tracker
<http://bugs.python.org/issue7
Changes by flox :
Removed file: http://bugs.python.org/file15585/issue7532_classic_getitem.diff
___
Python tracker
<http://bugs.python.org/issue7532>
___
___
Python-bug
flox added the comment:
Patch augmented with extensive tests:
* Classic class or New-style class
* with or without __getslice__
--
Added file: http://bugs.python.org/file15586/issue7532_classic_getitem_v2.diff
___
Python tracker
<h
flox added the comment:
Mark,
Thank you for your analysis.
I looked at similar implementation of tp_as_sequence->sq_slice slots in
"stringobject.c" (and tuple, list).
I've added extra controls before the _PySlice_FromIndices call to let it
behave like new-style classes.
New submission from flox :
See attached example.
The Classic class should behave like the New-style class.
--
components: Interpreter Core
files: case_slice.py
messages: 96520
nosy: flox
severity: normal
status: open
title: Extended slicing with classic class behaves strangely
type
Changes by flox :
Removed file: http://bugs.python.org/file15446/issue7381.diff
___
Python tracker
<http://bugs.python.org/issue7381>
___
___
Python-bugs-list mailin
Changes by flox :
Removed file: http://bugs.python.org/file15447/issue7381_py3k.diff
___
Python tracker
<http://bugs.python.org/issue7381>
___
___
Python-bugs-list mailin
Changes by flox :
Added file: http://bugs.python.org/file15581/issue7381_py3k_v2.diff
___
Python tracker
<http://bugs.python.org/issue7381>
___
___
Python-bugs-list mailin
flox added the comment:
Patch updated to backport r51536 in trunk.
It makes "python -3" happier (do not compare None >= 0).
--
Added file: http://bugs.python.org/file15580/issue7381_v2.diff
___
Python tracker
<http://bugs.pyth
flox added the comment:
It seems to behave correctly on 2.7 and 3.1 (svn versions).
$ ./python Tools/scripts/2to3 ../doublequote.py
RefactoringTool: Skipping implicit fixer: buffer
RefactoringTool: Skipping implicit fixer: idioms
RefactoringTool: Skipping implicit fixer: set_literal
flox added the comment:
Note: test_py3kwarn fails, probably since r76794.
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue7491>
___
___
Python-bug
flox added the comment:
This issue (and the patch) is to warn the tester that the flags and
environment variables are ignored.
Sorry for the DeprecationWarning noise, it is some silly test on my sandbox.
--
___
Python tracker
<h
flox added the comment:
Minimal patch proposed.
--
keywords: +patch
Added file: http://bugs.python.org/file15568/issue7516_regrtest_mp.diff
___
Python tracker
<http://bugs.python.org/issue7
New submission from flox :
~ $ ./python -3 Lib/test/regrtest.py -j2 test_py3kwarn
./Lib/encodings/__init__.py:100: DeprecationWarning:
the 'hex' codec has been removed in Python 3.0
level=0)
test_py3kwarn
test_py3kwarn skipped -- test.test_py3kwarn must be ru
Changes by flox :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue7092>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/m
New submission from flox :
~ $ ./python Lib/test/regrtest.py --help
(...)
lib2to3 - Run the tests for 2to3 (They take a while.)
(...)
~ $ ./python Lib/test/regrtest.py -ulib2to3
Invalid -u/--use option: lib2to3
Use --help for usage
--
components: Tests
messages: 96448
nosy: flox
New submission from flox :
Patch attached.
--
assignee: georg.brandl
components: Documentation
files: py3k_doc_sys_flags.diff
keywords: patch
messages: 96441
nosy: flox, georg.brandl
severity: normal
status: open
title: doc: documentation for "sys.flags" is obsolete.
versio
Changes by flox :
Added file: http://bugs.python.org/file15563/issue4770_binascii_py3k_v2.diff
___
Python tracker
<http://bugs.python.org/issue4770>
___
___
Python-bug
Changes by flox :
Removed file: http://bugs.python.org/file15562/issue4770_binascii_py3k_v2.diff
___
Python tracker
<http://bugs.python.org/issue4770>
___
___
Python-bug
flox added the comment:
Patch updated:
* Added documentation
* Switched to "payload.encode('ascii')" in the "email.message" module
Note: there was no ambiguity on the first line of the documentation:
« [These functions] convert between binary and various ASCII-
flox added the comment:
I perform a "grep" on the email package (with patch applied).
There's some places where 'raw-unicode-escape' is used.
I understand that all "payload.encode('raw-unicode-escape')" should be
changed to "payload.encode(
flox added the comment:
> Are you sure that this patch is correct (which RFC says
> that quoted printable should use our raw-unicode-escape
> codec ?):
I am not sure of anything. It is an "educated guess" at the most.
Since 'base64' and 'x-uuencode' both
flox added the comment:
This patch removes implicit encoding in binascii functions:
- a2b_hex (=unhexlify)
- a2b_qp
- rledecode_hqx
* Tests module "test_binascii" is reviewed and simplified.
* Fixes for "email", "pickle" and "quopri"
Changes by flox :
Removed file: http://bugs.python.org/file1/issue4757_zlib_bytes.diff
___
Python tracker
<http://bugs.python.org/issue4757>
___
___
Python-bugs-list m
flox added the comment:
I agree, we need consistency between all functions of this package.
I've run a small script to check what happens for all 16 functions of
the binascii package when they receive unicode input...
See attached script (and sample output).
IMHO 4 functions should be
flox added the comment:
Fixed.
And some "bytearray" tests improved in test_zlib.
--
Added file: http://bugs.python.org/file15556/issue4757_zlib_bytes_v2.diff
___
Python tracker
<http://bugs.python.
flox added the comment:
Patch from haypo updated for r76830 .
Additional tests for TypeError, and to check that bytearray objects are
accepted.
--
Added file: http://bugs.python.org/file1/issue4757_zlib_bytes.diff
___
Python tracker
<h
flox added the comment:
Definitely, zlib.compress should raise a TypeError (like bz2 does).
>>> import bz2, zlib
>>> bz2.compress('abc')
Traceback (most recent call last):
File "", line 1, in
TypeError: argument 1 must be bytes or buffer, not str
>&
Changes by flox :
Added file: http://bugs.python.org/file15553/issue6472_upstream_docs.diff
___
Python tracker
<http://bugs.python.org/issue6472>
___
___
Python-bug
Changes by flox :
Removed file: http://bugs.python.org/file15513/issue6472_upstream_docs.diff
___
Python tracker
<http://bugs.python.org/issue6472>
___
___
Python-bug
Changes by flox :
Removed file: http://bugs.python.org/file15471/issue6472_upstream_py3k.diff
___
Python tracker
<http://bugs.python.org/issue6472>
___
___
Python-bug
flox added the comment:
Small update of the patch for 3.2: the __cmp__method is replaced with
__eq__ method (on CommentProxy and PIProxy).
--
Added file: http://bugs.python.org/file15552/issue6472_upstream_py3k_v2.diff
___
Python tracker
<h
Changes by flox :
Added file: http://bugs.python.org/file15550/py3k_doc_faq_library.diff
___
Python tracker
<http://bugs.python.org/issue7499>
___
___
Python-bugs-list m
Changes by flox :
Removed file: http://bugs.python.org/file15549/py3k_doc_faq_library.diff
___
Python tracker
<http://bugs.python.org/issue7499>
___
___
Python-bugs-list m
Changes by flox :
Removed file: http://bugs.python.org/file15546/py3k_doc_faq_library.diff
___
Python tracker
<http://bugs.python.org/issue7499>
___
___
Python-bugs-list m
Changes by flox :
Added file: http://bugs.python.org/file15549/py3k_doc_faq_library.diff
___
Python tracker
<http://bugs.python.org/issue7499>
___
___
Python-bugs-list m
Changes by flox :
Added file: http://bugs.python.org/file15548/py3k_doc_faq_warnings.diff
___
Python tracker
<http://bugs.python.org/issue7500>
___
___
Python-bugs-list m
Changes by flox :
Removed file: http://bugs.python.org/file15547/py3k_doc_faq_warnings.diff
___
Python tracker
<http://bugs.python.org/issue7500>
___
___
Python-bug
New submission from flox :
I reviewed some FAQ documents: issue7493, issue7495 and issue7499
But other documents may be inaccurate.
We may add a warning at the top of these documents, until someone
volunteer to review them.
Patch attached.
--
assignee: georg.brandl
components
New submission from flox :
I reviewed the documentation and tested the examples with Python 3.
I found some import and print statements to change.
Here is the patch.
Note: I added a warning for the question "How do I get a single
keypress" (without curses). The solution may n
New submission from flox :
I reviewed the documentation and tested the examples with Python 3.
I found some parts which are changed or irrelevant.
Here is the patch.
The examples for Mandelbrot and Fibonacci work fine.
--
assignee: georg.brandl
components: Documentation
files
New submission from flox :
I reviewed the documentation and tested the examples with Python 3.
I found many parts which are changed or irrelevant.
Here is the patch.
--
assignee: georg.brandl
components: Documentation
files: py3k_doc_faq_design.diff
keywords: patch
messages: 96345
nosy
Changes by flox :
--
keywords: +patch
Added file: http://bugs.python.org/file15541/issue7492_cpickle.diff
___
Python tracker
<http://bugs.python.org/issue7
New submission from flox :
Word "cPickle" is still used on these pages.
http://docs.python.org/dev/py3k/library/shelve.html
http://docs.python.org/dev/py3k/library/copyreg.html
--
assignee: georg.brandl
components: Documentation
messages: 96342
nosy: flox, georg.brandl
severi
flox added the comment:
The bug seems related to Sphynx on Python3.
These examples are NOT colored::
class Z:
def __init__(self):
pass
::
class F:
def __foo__(self):
pass
::
class C:
def method(self):
pass
c = C()
c.method.__func__.whoami
New submission from flox :
Some code samples are not syntax colored in the doc for Python 3.
In the documentation for Python 2, it is OK.
Example:
http://docs.python.org/dev/py3k/library/stdtypes.html#methods
http://docs.python.org/dev/library/stdtypes.html#methods
--
assignee
flox added the comment:
> And this statement was not converted
s/this statement/this method call/
--
___
Python tracker
<http://bugs.python.org/iss
flox added the comment:
Martin,
actually, I was trying to convert some piece of code from python2 to
python3. And this statement was not converted by 2to3:
"x.decode('base64').decode('zlib')"
So, I read the official documentation, and found no hint about the
r
Changes by flox :
--
keywords: +patch
Added file: http://bugs.python.org/file15531/issue7486_doc_py3k.diff
___
Python tracker
<http://bugs.python.org/issue7
New submission from flox :
In the documentation of "compile(...)", there's a mention of the "exec
statement".
--
assignee: georg.brandl
components: Documentation
messages: 96293
nosy: flox, georg.brandl
severity: normal
status: open
title: doc: Built-in Fun
Changes by flox :
--
versions: -Python 3.0
___
Python tracker
<http://bugs.python.org/issue7380>
___
___
Python-bugs-list mailing list
Unsubscribe:
flox added the comment:
I've ported the codecs from Py2:
base64, bytes_escape, bz2, hex, quopri, rot13, uu and zlib
It's not a big deal. Basically:
- StringIO.StringIO --> io.BytesIO
- 'string_escape' --> 'bytes_escape'
Will add docu
flox added the comment:
Ok. It is here:
http://bugs.python.org/file15520/issue7466.diff
--
___
Python tracker
<http://bugs.python.org/issue7466>
___
___
Pytho
flox added the comment:
Thinking about it, I am +1 to reimplement the codecs.
We could implement new methods to replace the old one.
(similar to base64.encodebytes and base64.decodebytes)
>>> b'abc'.encodebytes('base64')
b'YWJj\n'
>>>
Changes by flox :
--
keywords: +patch
Added file: http://bugs.python.org/file15523/issue7475_warning.diff
___
Python tracker
<http://bugs.python.org/issue7
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
Changes by flox :
--
versions: +Python 2.7
___
Python tracker
<http://bugs.python.org/issue7475>
___
___
Python-bugs-list mailing list
Unsubscribe:
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
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
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
Changes by flox :
Added file: http://bugs.python.org/file15521/issue7466.diff
___
Python tracker
<http://bugs.python.org/issue7466>
___
___
Python-bugs-list mailin
Changes by flox :
Removed file: http://bugs.python.org/file15520/issue7466.diff
___
Python tracker
<http://bugs.python.org/issue7466>
___
___
Python-bugs-list mailin
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
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:
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:
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
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:
(removed comment which should not be copied)
--
Added file: http://bugs.python.org/file15507/fastsearch_rfind.patch
___
Python tracker
<http://bugs.python.org/issue7
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:
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
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:
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', '
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:
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 :
--
versions: +Python 2.7
___
Python tracker
<http://bugs.python.org/issue5596>
___
___
Python-bugs-list mailing list
Unsubscribe:
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
flox added the comment:
Patch for the test refleaks:
* test_pipes
* test_urllib
--
___
Python tracker
<http://bugs.python.org/issue5596>
___
___
Python-bug
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
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
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 :
Removed file: http://bugs.python.org/file15469/issue6472_upstream_py3k.diff
___
Python tracker
<http://bugs.python.org/issue6472>
___
___
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/file15470/issue1143_ET13_cET106.diff
___
Python tracker
<http://bugs.python.org/issue1143>
___
___
Python-bug
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/file15461/issue6472.diff
___
Python tracker
<http://bugs.python.org/issue6472>
___
___
Python-bugs-list mailin
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 :
--
versions: -Python 3.0
Added file: http://bugs.python.org/file15469/issue6472_upstream_py3k.diff
___
Python tracker
<http://bugs.python.org/issue6
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 :
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:
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
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
Changes by flox :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue6472>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/m
Changes by flox :
--
versions: +Python 2.6, Python 3.1, Python 3.2
___
Python tracker
<http://bugs.python.org/issue6058>
___
___
Python-bugs-list mailin
1 - 100 of 162 matches
Mail list logo
