[issue7551] SystemError/MemoryError/OverflowErrors on encode() a unicode string

Marc-Andre Lemburg added the comment: All string length calculations in Python 2.4 are done using ints which are 32-bit, even on 64-bit platforms. Since UTF-8 can use up to 4 bytes per Unicode code point, the encoder overallocates the needed chunk of memory to len*4 bytes. This will go straight

[issue7555] Wrong return value of isinstance() function

New submission from Leo Spidian : isinstance() function returns False while surpposed to return True tt.py = import ss class tt: def __init__(self, s): if not isinstance(s, ss.ss): raise Exception("s is not an instance of ss.ss") ==

[issue7555] Wrong return value of isinstance() function

Changes by Leo Spidian : Removed file: http://bugs.python.org/file15641/ss.py ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscr

[issue7555] Wrong return value of isinstance() function

Changes by Leo Spidian : Added file: http://bugs.python.org/file15642/ss.py ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue7555] Wrong return value of isinstance() function

Changes by Leo Spidian : Added file: http://bugs.python.org/file15643/tt.py ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue7555] Wrong return value of isinstance() function

Mark Dickinson added the comment: While I agree it's confusing, I think this is working as designed. The problem is coming from the circular import. If you add a "print id(ss)" between the definition of class ss and the "if __name__ == '__main__'" you'll see that ss ends up being defined tw

[issue7482] Improve ZeroDivisionError message for float and complex object

Retro added the comment: The patch is *almost* okay. errno = 0; div = c_quot(v->cval,w->cval); /* The raw divisor value. */ if (errno == EDOM) { - PyErr_SetString(PyExc_ZeroDivisionError, "complex remainder"); + PyErr_SetString(PyExc_ZeroDivisionError

[issue7555] Wrong return value of isinstance() function

Leo Spidian added the comment: Thank you very much! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue7528] Provide PyLong_AsLongAndOverflow compatibility to Python 2.x

Mark Dickinson added the comment: Perfect---thank you! Applied to trunk in r76963. I tweaked the main comment and docstring, wrapped a long line, and replaced two instances of '*overflow = Py_SIZE(v) > 0 ? 1 : -1' with simply '*overflow = sign'. I also expanded the test a bit to check for

[issue7462] Implement fastsearch algorithm for rfind/rindex

Florent Xicluna added the comment: Updated patch with optimization for: * rfind * rindex * rsplit * rpartition And an optimization was implemented in r46398 but never used because "#define USE_FAST" was removed 2 hours before: r46366. ==> I changed this to activate optimization on "S.split"

[issue7462] Implement fastsearch algorithm for rfind/rindex

Florent Xicluna added the comment: Actually, the USE_FLAG macro was removed in r46367 (not 46366). « needforspeed: remove remaining USE_FAST macros; if fastsearch was broken, someone would have noticed by now ;-) » -- ___ Python tracker

[issue7462] Implement fastsearch algorithm for rfind/rindex

Changes by Florent Xicluna : Removed file: http://bugs.python.org/file15507/fastsearch_rfind.patch ___ Python tracker ___ ___ Python-bugs-list

[issue7033] C/API - Document exceptions

lekma added the comment: patch against trunk: - fix tabs issue (I hope) - add test -- Added file: http://bugs.python.org/file15645/issue7033_trunk_3.diff ___ Python tracker ___ _

[issue7033] C/API - Document exceptions

lekma added the comment: The same with a simpler test. I leave it up to you guys to choose which one is the best. -- Added file: http://bugs.python.org/file15646/issue7033_trunk_3_alt_test.diff ___ Python tracker _

[issue6108] unicode(exception) and str(exception) should return the same message on Py2.6

Antoine Pitrou added the comment: > I created a comprehensive set of tests to check all the possibilities > that I listed in msg96319 and updated the patch for Object/exceptions.c. Great! Small thing: in tests, you should use setUp() to initialize test data rather than __init__(). --

[issue7462] Implement fastsearch algorithm for rfind/rindex

Changes by Florent Xicluna : Removed file: http://bugs.python.org/file15644/fastsearch_rfind_v2.patch ___ Python tracker ___ ___ Python-bugs-li

[issue7462] Implement fastsearch algorithm for rfind/rindex

Florent Xicluna added the comment: I reupload the patch fixed (sorry). -- Added file: http://bugs.python.org/file15647/issue7462_fastsearch_v2.diff ___ Python tracker ___ ___

[issue7555] Wrong return value of isinstance() function

R. David Murray added the comment: Just to be clear, this isn't a case of circular imports, but of the class being defined twice (as two different objects, as Mark said), once when the module is created as main when ss.py is run, and the other when ss is imported for the first time (by tt). You

[issue7555] Wrong return value of isinstance() function

Mark Dickinson added the comment: Much better explanation! Thanks, David. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue7528] Provide PyLong_AsLongAndOverflow compatibility to Python 2.x

Mark Dickinson added the comment: I fixed up py3k to be in sync with trunk, and added your tests (slightly expanded) to py3k in r76971. Thanks! -- resolution: -> accepted status: open -> closed ___ Python tracker

[issue7462] Implement fastsearch algorithm for rfind/rindex

Antoine Pitrou added the comment: Some things: - is STRINGLIB_CMP still used? if not, it should be removed (use grep :-)) - please don't use "#if 1" - if USE_FAST isn't used anymore, it should be remove as well - did you check that rpartition, split and friends were sped up by the patch? Thanks

[issue7462] Implement fastsearch algorithm for rfind/rindex

Florent Xicluna added the comment: Actually I see different macros which do the same thing: I will consider reusing STRINGLIB_CMP to re-define PyUNICODE_MATCH and PySTRING_MATCH (or create aliases if they have the same signature). I can prepare a "all-in-one" patch which fixes all these things.

[issue7462] Implement fastsearch algorithm for rfind/rindex

Antoine Pitrou added the comment: > Actually I see different macros which do the same thing: I will consider > reusing STRINGLIB_CMP to re-define PyUNICODE_MATCH and PySTRING_MATCH > (or create aliases if they have the same signature). STRINGLIB_CMP, as the name implies, should only be used by

[issue7462] Implement fastsearch algorithm for rfind/rindex

Florent Xicluna added the comment: Removing "slow" parts and unnused macros STRINGLIB_CMP and USE_FAST. -- Added file: http://bugs.python.org/file15648/issue7462_fastsearch_v3.diff ___ Python tracker __

[issue7462] Implement fastsearch algorithm for rfind/rindex

Changes by Florent Xicluna : Removed file: http://bugs.python.org/file15647/issue7462_fastsearch_v2.diff ___ Python tracker ___ ___ Python-bugs

[issue5080] PyArg_Parse* should raise TypeError for float parsed with integer format

Mark Dickinson added the comment: Here's a patch that makes the DeprecationWarning a TypeError, and adds a new DeprecationWarning for the 'L' format. -- keywords: +patch Added file: http://bugs.python.org/file15649/issue5080.patch ___ Python tracker

[issue7497] configure test for posix_semaphore capability leaves semaphore behind, causing test to fail for other users

Mark Dickinson added the comment: This seems to be fixed; I think I must have had a stale semaphore lying around, from while I was experimenting with the original problem. -- status: open -> closed ___ Python tracker

[issue7550] PyLong_As* methods should not call nb_int.

Mark Dickinson added the comment: It turns out this is intimately bound up with the behaviour of PyArg_ParseTuple* for integer format codes. Since this behaviour can't change until Python 3.3 (because of the moratorium), I'm closing this for now. -- resolution: -> later status: ope

[issue7518] Some functions in pymath.c should be moved elsewhere.

Mark Dickinson added the comment: Moved atanh, asinh, acosh, log1p from pymath.c to Modules/_math.c in r76978 (trunk), r76980 (py3k). -- assignee: -> mark.dickinson priority: -> normal resolution: -> fixed status: open -> closed ___ Python tracke

[issue6108] unicode(exception) and str(exception) should return the same message on Py2.6

Ezio Melotti added the comment: I updated the patch and moved the helper class outside the __init__. -- Added file: http://bugs.python.org/file15650/issue6108-5.patch ___ Python tracker

[issue6108] unicode(exception) and str(exception) should return the same message on Py2.6

Antoine Pitrou added the comment: This looks fine, module the slight style issue mentioned on IRC. Please commit after you fix it. (this is assuming all tests pass, of course!) -- resolution: -> accepted stage: patch review -> commit review ___ Pyth

[issue7462] Implement fastsearch algorithm for rfind/rindex

Antoine Pitrou added the comment: I haven't reviewed the algorithm (I don't know if I will, honestly), but at least on the principle this looks good. Fredrik, do you want to take a look? -- nosy: +effbot ___ Python tracker

[issue6058] Add cp65001 to encodings/aliases.py

Antoine Pitrou added the comment: (I tried running your script under IronPython 2.6 with Mono but I got a bunch of errors; since I don't know IronPython at all I can't really investigate) -- nosy: +pitrou ___ Python tracker

[issue7553] test_long_future is faulty

Mark Dickinson added the comment: Applied in r76984. Thanks! -- nosy: +mark.dickinson resolution: -> fixed status: open -> closed ___ Python tracker ___ ___

[issue7544] multiprocessing.Pool(): Fatal Python error: PyEval_AcquireThread: NULL new thread state

Antoine Pitrou added the comment: We just had this error on one of the buildbots: [...] test_threadsignals sem_wait: Unknown error 512 test_docxmlrpc Fatal Python error: Invalid thread state for this thread Fatal Python error: PyEval_AcquireThread: non-NULL old thread state make: *** [buildbott

[issue7534] float('nan')**2 != nan. float('nan')**2 error 33 on windows

Changes by Mark Dickinson : -- stage: needs patch -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue6108] unicode(exception) and str(exception) should return the same message on Py2.6

Ezio Melotti added the comment: This should be the final patch (issue6108-6.patch). I update the comments, checked that (some of) the tests fail without the patch, that they (all) pass with it and that there are no leaks. I plan to backport this on 2.6 and possibly port the tests to py3k and 3.1

[issue6108] unicode(exception) and str(exception) should return the same message on Py2.6

Antoine Pitrou added the comment: It's ok for me. -- resolution: -> accepted stage: patch review -> commit review ___ Python tracker ___

[issue7462] Implement fastsearch algorithm for rfind/rindex

Changes by Florent Xicluna : Removed file: http://bugs.python.org/file15637/stringbench_rfind_rindex.diff ___ Python tracker ___ ___ Python-bug

[issue7462] Implement fastsearch algorithm for rfind/rindex

Changes by Florent Xicluna : Added file: http://bugs.python.org/file15652/stringbench_fixes_and_additions.diff ___ Python tracker ___ ___ Pyth

[issue7462] Implement fastsearch algorithm for rfind/rindex

Changes by Florent Xicluna : Removed file: http://bugs.python.org/file15652/stringbench_fixes_and_additions.diff ___ Python tracker ___ ___ Py

[issue7556] msvc9compiler.py: TypeError: can't use a string pattern on a bytes-like object

New submission from Sridhar Ratnakumar : While building pywin32 with Py3k trunk (not release version), I get this traceback: Creating library build\temp.win32- 3.1\Release\win32\src\pywintypes31.lib and object buil d\temp.win32-3.1\Release\win32\src\pywintypes31.exp Traceback (most recent ca

[issue7556] msvc9compiler.py: TypeError: can't use a string pattern on a bytes-like object

Sridhar Ratnakumar added the comment: Uh, cmd.exe seemed to have stripped some chars. Here's the full traceback: http://gist.github.com/261153 -- ___ Python tracker ___

[issue7556] msvc9compiler.py: TypeError: can't use a string pattern on a bytes-like object

Sridhar Ratnakumar added the comment: Correction: I found this in branches/release3.1-maint (not trunk - which I never tried) -- ___ Python tracker ___ _

[issue7556] msvc9compiler.py: TypeError: can't use a string pattern on a bytes-like object

Stefan Krah added the comment: I also raised this issue at the end of issue 4120 (which is closed). I'll post the diff here, too. -- keywords: +patch nosy: +skrah versions: +Python 3.1 Added file: http://bugs.python.org/file15653/3.1-byte-string.diff ___

[issue7557] Imprecise description for the fire.read() method

New submission from Jacques Lemire : see this web page: http://docs.python.org/3.1/library/stdtypes.html? highlight=read#file.read The description should say: for Python 3.1 the method reads characters, for instance utf-8 characters. if the mode is 'rb', then it reads bytes (i.e. byte == 8 bit

[issue7558] Python 3.1.1 installer botches upgrade when installation is not on C drive.

New submission from John Nagle : I just installed "python3.1.1.msi" on a system that had "python3.1.msi" installed in "D:/python31". In this situation, the installer does not ask the user for a destination directory. The installer found the old installation in "D:/python31", removed most but no

[issue4120] Do not embed manifest files in *.pyd when compiling with MSVC

Sridhar Ratnakumar added the comment: See issue 7556 for the "can't use a string pattern on a bytes-like object" error. -- nosy: +srid ___ Python tracker ___ ___

[issue7462] Implement fastsearch algorithm for rfind/rindex

Changes by Florent Xicluna : Added file: http://bugs.python.org/file15654/stringbench_fixes_and_additions_v2.diff ___ Python tracker ___ ___ P

[issue7559] TestLoader.loadTestsFromName swallows import errors

New submission from Robert Collins : Say I have a test module test_foo, which fails to import with ImportError. A reason for this might be a misspelt import in that module. TestLoader().loadTestsFromName swallows the import error and instead crashes with: File "/usr/lib/python2.6/unittest.py",

[issue7462] Implement fastsearch algorithm for rfind/rindex

Changes by Florent Xicluna : Removed file: http://bugs.python.org/file15654/stringbench_fixes_and_additions_v2.diff ___ Python tracker ___ ___

[issue7462] Implement fastsearch algorithm for rfind/rindex

Changes by Florent Xicluna : Added file: http://bugs.python.org/file15655/stringbench_fixes_and_additions_v3.diff ___ Python tracker ___ ___ P

[issue7462] Implement fastsearch algorithm for rfind/rindex

Florent Xicluna added the comment: New benchmarks (and patch for the benchmark tool). Best improvement is reached with such expression: s="ABC"*33; (s+"E"+("D"+s)*500).rfind(s+"E") (*100) String (classic): 93.14 ms String (fast): 8.78 ms Unicode (classic): 78.62 ms Unicode (fast): 9

[issue7462] Implement fastsearch algorithm for rfind/rindex

Changes by Florent Xicluna : Removed file: http://bugs.python.org/file15638/bench_rfind_algorithms_v2.diff ___ Python tracker ___ ___ Python-bu

[issue7557] Imprecise description for the file.read() method

Florent Xicluna added the comment: This section is obsolete and is removed from the documentation in r76893 an r76894. See issue #7508. -- nosy: +flox resolution: -> duplicate stage: -> committed/rejected status: open -> closed superseder: -> Update 'file object' doc title: Imprecise

[issue7558] Python 3.1.1 installer botches upgrade when installation is not on C drive.

Martin v. Löwis added the comment: I can't reproduce this; the 3.1.1 installer will most certainly ask for a target directory even if there is a 3.1 installation already; see the attached screenshot. I'm slightly puzzled by the file names you report, as the files on python.org have dashes in the

[issue7559] TestLoader.loadTestsFromName swallows import errors

R. David Murray added the comment: Could you provide a more complete recipe for reproducing the problem, please? I created a test_foo.py containing 'import blert', and running python -m unittest test_foo does not mask the import error for blert in loadTestsFromName: ... File "/usr/lib/python

[issue7514] doc: documentation for "sys.flags" is obsolete.

Changes by Florent Xicluna : -- priority: -> low stage: -> patch review type: -> behavior ___ Python tracker ___ ___ Python-bugs-lis

[issue7556] msvc9compiler.py: TypeError: can't use a string pattern on a bytes-like object

Tarek Ziadé added the comment: Stefan's patch will do the trick. I am adding a test to make sure this part is covered before I apply the patch -- nosy: +loewis ___ Python tracker ___

[issue7537] test_format fails with -j combined with -v

Changes by Florent Xicluna : -- stage: needs patch -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue7556] msvc9compiler.py: TypeError: can't use a string pattern on a bytes-like object

Martin v. Löwis added the comment: I'd rather prefer if the manifest was opened in text mode. It should be UTF-8 encoded (although ASCII would work as well). -- ___ Python tracker __

[issue7455] cPickle: stack underflow in load_pop()

Changes by Florent Xicluna : -- priority: -> normal stage: test needed -> patch review ___ Python tracker ___ ___ Python-bugs-list mai

[issue7559] TestLoader.loadTestsFromName swallows import errors

Robert Collins added the comment: mkdir thing touch thing/__init__.py echo "import blert" > thing/test_foo.py python -m unittest thing.test_fooTraceback (most recent call last): File "/usr/lib/python2.6/runpy.py", line 122, in _run_module_as_main "__main__", fname, loader, pkg_name) File

[issue7544] multiprocessing.Pool(): Fatal Python error: PyEval_AcquireThread: NULL new thread state

STINNER Victor added the comment: No, I don't think that this issue is related, because it starts with another message: "Invalid thread state for this thread". -- ___ Python tracker

[issue7556] msvc9compiler.py: TypeError: can't use a string pattern on a bytes-like object

Tarek Ziadé added the comment: sure, that's even simpler. I am adding a test and this simple fix. Notice that this code could be replaced with some code that uses an xml parser. I find the regexp patterns a bit inappropriate here because it removes "" in a second call, but may leave an empty ""

[issue7556] msvc9compiler.py: TypeError: can't use a string pattern on a bytes-like object

Martin v. Löwis added the comment: As for using proper XML processing: that would be fine as well. As for leaving an empty dependency element: in the original report, MAL says that this is conforming. I found a schema file (from MS) which agrees, and a textual documentation page that disagrees.

[issue7557] Imprecise description for the file.read() method

Jacques Lemire added the comment: Merci Florent Mais alors où se cache la documentation 3.1 "officiel" sur la classe file. Jacques 2009/12/21 Florent Xicluna > > Florent Xicluna added the comment: > > This section is obsolete and is removed from the documentation in r76893 > an r76894. See

[issue7557] Imprecise description for the file.read() method

Antoine Pitrou added the comment: It's in the "io" module: http://docs.python.org/dev/py3k/library/io.html -- nosy: +pitrou ___ Python tracker ___ ___

[issue7557] Imprecise description for the file.read() method

Georg Brandl added the comment: > Merci Florent > Mais alors où se cache la documentation 3.1 "officiel" sur la classe file. Even though we seem to have a disturbing accumulation of French developers here, please keep to English on the tracker :) -- ___

[issue7556] msvc9compiler.py: TypeError: can't use a string pattern on a bytes-like object

Tarek Ziadé added the comment: Ok thanks for the detailed info, Martin I guess we could refactor it to an xml reader/writer if we need to do more things in the future with these files. I'll close this issue, as the mentioned problem is now fixed by using a text mode. The test in test_msvc9comp

[issue6900] Sub-optimal "Locate" button behaviour in Windows CHM file

Adal Chiriliuc added the comment: This seem to have been broken when the help file style was changed (from 2.5 to 2.6). I'm also bothered by this issue, since you cannot locate easily now related modules. For example, in the old help version I would go in the index to urllib, display the modul

[issue7558] Python 3.1.1 installer botches upgrade when installation is not on C drive.

John Nagle added the comment: Cancel bug report. It was my error. The installer says it is replacing the existing installation, but by default installs it in C:. But that can be overridden in the directory entry field below the big empty white entry box. -- __

[issue7559] TestLoader.loadTestsFromName swallows import errors

R. David Murray added the comment: Thank you. I can reproduce this on trunk as well. I'm leaving stage set to test needed because we need to turn this into a unit test. -- keywords: +easy versions: +Python 2.7, Python 3.1, Python 3.2 ___ Python tra

[issue7559] TestLoader.loadTestsFromName swallows import errors

R. David Murray added the comment: Note: this problem is similar in some ways to issue 5230, and a similar solution might be appropriate (or might not :). -- ___ Python tracker _

[issue7559] TestLoader.loadTestsFromName swallows import errors

Michael Foord added the comment: I'll try and look at both these issues in the next few days unless one of you beats me to it. :-) -- ___ Python tracker ___ _

[issue7558] Python 3.1.1 installer botches upgrade when installation is not on C drive.

Changes by Martin v. Löwis : -- resolution: -> invalid status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue7559] TestLoader.loadTestsFromName swallows import errors

Robert Collins added the comment: I'm scratching an itch at the moment, I just noted this in passing ;) I'm partial to the 'turn it into a fake test case' approach, its what I would do if I get to it first. -- ___ Python tracker

[issue1673007] urllib2 requests history + HEAD support

Senthil Kumaran added the comment: Here is a discussion and explanation from the submitter on what is meant by history of requests. http://mail.python.org/pipermail/python-dev/2007-March/072069.html -- ___ Python tracker

[issue7560] Various filename-taking posix methods don't like bytes / buffer objects.

New submission from Sebastian Hagen : Most of the functions in Python's stdlib that take filename parameters allow for those parameters to be buffer (such as bytes, bytearray, memoryview) objects. This is useful for various reasons, among them that on Posix-likes, file- and pathnames ultimately *

[issue7560] Various filename-taking posix methods don't like bytes / buffer objects.

Changes by Sebastian Hagen : -- type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue7560] Various filename-taking posix methods don't like bytes / buffer objects.

Changes by Sebastian Hagen : Removed file: http://bugs.python.org/file15659/posix_fn_bytes_01.patch ___ Python tracker ___ ___ Python-bugs-list

[issue7560] Various filename-taking posix methods don't like bytes / buffer objects.

Sebastian Hagen added the comment: I'm taking that patch back. More testing would have been in order before posting; sorry for that, will repost once I've got the obvious problems worked out. -- ___ Python tracker

[issue7560] Various filename-taking posix methods don't like bytes / buffer objects.

Sebastian Hagen added the comment: And further testing reveals that all of this has in fact already been fixed in trunk. I assumed it hadn't been, because the code for at least some of the relevant functions in Modules/_posixmodule.c is the same as in 3.1.1; I didn't know that the samentics for

[issue7560] Various filename-taking posix methods don't like bytes / buffer objects.

Changes by Sebastian Hagen : -- status: open -> closed versions: -Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue7561] Filename-taking functions in posix segfault when called with a bytearray arg.

New submission from Sebastian Hagen : Various functions in the 'posix' module that take filename arguments accept bytearray values for those arguments, and mishandle those objects in a way that leads to segfaults. Python 3.1 (r31:73572, Jul 23 2009, 23:41:26) [GCC 4.3.3] on linux2 Type "help", "