[issue15444] Incorrectly writen contributor's names

Martin v. Löwis added the comment: There was a long-standing opposition by Guido to use UTF-8 in that file, and also complaints about legibility. Not sure what the current status is. It doesn't matter much to me, even though the spelling of my name is affected. -- ___

[issue15445] Ability to do code injection via logging module configuration listener port.

Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue15444] Incorrectly written contributor's names

Serhiy Storchaka added the comment: Well, here is updated patch. Also fixed names of Walter Dörwald (was Walter D�rwald) and Martin von Löwis in Misc/HISTORY. All changed files (documentation, ACK-files, Misc/HISTORY) already in UTF-8 and contains non-ASCII names. Löwis written as Loewis in

[issue15443] datetime module has no support for nanoseconds

STINNER Victor added the comment: See the PEP 410. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue15441] test_posixpath fails on Japanese edition of Windows

STINNER Victor added the comment: The following change is a major change on how Python handles undecodable filenames on Windows: -return PyUnicode_DecodeMBCS(s, size, NULL); +return PyUnicode_DecodeMBCS(s, size, "surrogateescape"); I disagree with this change, Python should not genera

[issue15402] Correct __sizeof__ support for struct

Mark Dickinson added the comment: [Martin] > The patch that Meador committed is incorrect: METH_NOARGS functions > still take a PyObject* args argument, which will be NULL. Hmm. I see this usage in a lot of places---e.g. see unicode_capitalize, unicode_casefold, unicode_title etc. in Objects/

[issue15443] datetime module has no support for nanoseconds

Marc-Andre Lemburg added the comment: Vincenzo Ampolo wrote: > > Vincenzo Ampolo added the comment: > > This is a real use case I'm working with that needs nanosecond precision > and lead me in submitting this request: > > most OSes let users capture network packets (using tools like tcpdump

[issue15441] test_posixpath fails on Japanese edition of Windows

STINNER Victor added the comment: > If a file name was invalid byte character, os.chdir() raises > UnicodeDecodeError() instead of WindowsError. I realized that the problem is in the error handling: raising the OSError fails with a UnicodeDecodeError because PyErr_SetFromWindowsErrWithFilename

[issue15441] test_posixpath fails on Japanese edition of Windows

Atsuo Ishimoto added the comment: Yes, I know #13374, that's why I wrote > This is a byte-api issue on Windows, so we may be able to simply skip > this test. Do you think we need a patch to avoid UnicodeDecodeError raised? Or should we change test to skip this? -- _

[issue15444] Incorrectly written contributor's names

Marc-Andre Lemburg added the comment: Thank you for taking the initiative. Regarding use of UTF-8 for text files: I think we ought to acknowledge that UTF-8 has become the defacto standard for non-ASCII text files by now and with Python 3 being all Unicode, it feels silly not make use of it in

[issue15318] IDLE - sys.stdin is writeable

Roundup Robot added the comment: New changeset a82fd35e28be by Martin v. Löwis in branch '3.2': Issue #15318: Prevent writing to sys.stdin. http://hg.python.org/cpython/rev/a82fd35e28be -- nosy: +python-dev ___ Python tracker

[issue15318] IDLE - sys.stdin is writeable

Roundup Robot added the comment: New changeset fa7d4ecc6357 by Martin v. Löwis in branch '2.7': Issue #15318: Prevent writing to sys.stdin. http://hg.python.org/cpython/rev/fa7d4ecc6357 -- ___ Python tracker _

[issue15318] IDLE - sys.stdin is writeable

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

[issue15438] Incredible issue in math.pow

Mark Dickinson added the comment: Agreed that this is at worst a doc issue. [Antoine] > and in all honesty I don't know the difference between the "**" operator > and the built-in pow() function :-) None, as far as I know, apart from the pow function's ability to take a 3rd argument. Both ul

[issue15402] Correct __sizeof__ support for struct

Martin v. Löwis added the comment: > I will happily fix it, but if it is wrong one place, then it is wrong > everywhere. Yes, it is wrong everywhere. METH_NOARGS functions do take an args argument, see ceval.c:call_function. -- ___ Python tracker <

[issue15402] Correct __sizeof__ support for struct

Martin v. Löwis added the comment: > Hmm. I see this usage in a lot of places---e.g. see > unicode_capitalize, unicode_casefold, unicode_title etc. in > Objects/unicodeobject.c. So it looks like we're relying on the > (PyCFunction) cast to convert from a one-argument function pointer to > a tw

[issue15441] test_posixpath fails on Japanese edition of Windows

STINNER Victor added the comment: > Do you think we need a patch to avoid UnicodeDecodeError raised? > Or should we change test to skip this? It's a bug, the test should not be skipped. You should get an OSError because the chdir() failed, not an UnicodeDecodeError. -- ___

[issue15441] test_posixpath fails on Japanese edition of Windows

Martin v. Löwis added the comment: As for your patch: you are missing the point of the test. The file name is assumed to be valid, despite it not being in the file system encoding. -- ___ Python tracker _

[issue15441] test_posixpath fails on Japanese edition of Windows

Martin v. Löwis added the comment: IMO, it is ok to skip the test on Windows; it was apparently targeted for Unix. If we preserve it, we should pick a file name (on Windows) which is encodable in the file system encoding. -- ___ Python tracker

[issue7163] IDLE suppresses sys.stdout.write() return value

Roundup Robot added the comment: New changeset f72965374b2a by Martin v. Löwis in branch '3.2': Issue #7163: Propagate return value of sys.stdout.write. http://hg.python.org/cpython/rev/f72965374b2a -- nosy: +python-dev ___ Python tracker

[issue7163] IDLE suppresses sys.stdout.write() return value

Martin v. Löwis added the comment: Thanks for the patch! -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Py

[issue15446] Recursion SIGSEGV

New submission from Arseniy : a=lambda:a print eval("a" + "()" * 99) -- components: None messages: 166378 nosy: senyai priority: normal severity: normal status: open title: Recursion SIGSEGV type: crash versions: Python 2.7, Python 3.3 ___ Python

[issue15363] Idle/tkinter ~x.py 'save as' fails. closes idle

Martin v. Löwis added the comment: I think this should apply to all systems, and I think the proper escaping is with "./", see TclpNativeSplitPath (in Tcl's source code). -- nosy: +loewis ___ Python tracker _

[issue15402] Correct __sizeof__ support for struct

Mark Dickinson added the comment: > The compiler has no chance to find out. You cast the pointer to > PyCFunction, telling the compiler that it really is a PyCFunction. True; I was thinking that the compiler should have the necessary information to warn about the suspicious (PyCFunction) cast.

[issue14930] Make memoryview weakrefable

Stefan Krah added the comment: A quick question: Prior to this patch test_memoryview.py exercised both mbuf_clear() and memory_clear(). Now gcov shows no coverage. Is this expected? Is it still possible to construct tests that exercise the code? --

[issue15445] Ability to do code injection via logging module configuration listener port.

Vinay Sajip added the comment: I think it is sufficient for 2.7, 3.2 and 3.3 to just update the documentation, as Graham says, using "note" markup so that it stands out. I can look at ast.literal_eval as an option for 3.4. -- ___ Python tracker

[issue15443] datetime module has no support for nanoseconds

Alexander Belopolsky added the comment: On Wed, Jul 25, 2012 at 4:17 AM, Marc-Andre Lemburg wrote: > ... full C double precision for the time part of a timestamp, > which covers nanoseconds just fine. No, it does not: >>> import time >>> t = time.time() >>> t + 5e-9 == t True In fact, C dou

[issue15402] Correct __sizeof__ support for struct

Stefan Krah added the comment: ""Everywhere" is nowhere close to the truth. There are tons of NOARGS functions which have the correct signature." When I started writing C-extensions, I used the PyObject *unused idiom. Then I saw Meador's version in so many places in the source tree that I assum

[issue15443] datetime module has no support for nanoseconds

Marc-Andre Lemburg added the comment: Marc-Andre Lemburg wrote: > >> Alexander Belopolsky added the comment: >> >> On Wed, Jul 25, 2012 at 4:17 AM, Marc-Andre Lemburg >> wrote: >>> ... full C double precision for the time part of a timestamp, >>> which covers nanoseconds just fine. >> >> No,

[issue15446] Eval Recursion SIGSEGV

Changes by R. David Murray : -- resolution: -> duplicate stage: -> committed/rejected status: open -> closed superseder: -> stack overflow evaluating eval("()" * 3) title: Recursion SIGSEGV -> Eval Recursion SIGSEGV ___ Python tracker

[issue15443] datetime module has no support for nanoseconds

Marc-Andre Lemburg added the comment: Alexander Belopolsky wrote: > > Alexander Belopolsky added the comment: > > On Wed, Jul 25, 2012 at 4:17 AM, Marc-Andre Lemburg > wrote: >> ... full C double precision for the time part of a timestamp, >> which covers nanoseconds just fine. > > No, it

[issue15443] datetime module has no support for nanoseconds

Marc-Andre Lemburg added the comment: [Roundup's email interface again...] x = 86400.0 x == x + 1e-9 > False x == x + 1e-10 > False x == x + 1e-11 > False x == x + 1e-12 > True -- ___ Python tracker

[issue15424] __sizeof__ of array should include size of items

Ludwig Hähne added the comment: Revised the patch based on the discussion in issue #15402 (http://bugs.python.org/msg166372). It doesn't typecast the function anymore and instead casts to the array type inside the function. -- Added file: http://bugs.python.org/file26510/array_sizeof_

[issue15402] Correct __sizeof__ support for struct

Jesús Cea Avión added the comment: I think that C standard actually documents the parameter order placement, so you can left out the last ones in the actual function definition. So, that this is working is not an accident, it is a C standard requirement. I think... -- __

[issue15275] isinstance is called a more times that needed in ntpath

Ezio Melotti added the comment: > I don't know about a decent way of doing benchmarks for the changes. > Any recommendation? You could make a script that uses the timeit module. >> If this patch is applied I think it would be good to change >> posixpath too. > I agree and I'd love to do it but

[issue15402] Correct __sizeof__ support for struct

Martin v. Löwis added the comment: Jesús: this is a (common) mistake. Standard C makes it undefined behavior to call a function with an incorrect number of arguments, see 6.5.2.2p9 # If the function is defined with a type that is not compatible with the # type (of the expression) pointed to by

[issue15447] A file is not properly closed by webbrowser._invoke

New submission from Anton Barkovsky : webbrowser._invoke opens /dev/null, never closes it and a warning is printed. I'm attaching a patch. The diff looks messy, but I'm just wrapping the code in a try-finally block, the rest is just indented. -- components: Library (Lib) files: fileclos

[issue15402] Correct __sizeof__ support for struct

Martin v. Löwis added the comment: Stefan: not sure whether raising this to python-dev really helps; see also msg42177, msg58196, issue1648268, and msg75239. Feel free to raise it, though. -- ___ Python tracker

[issue15447] A file is not properly closed by webbrowser._invoke

R. David Murray added the comment: Thanks. Is this warning printed by the webbrowser unit tests? If not can you see a way to add one that does? -- nosy: +r.david.murray ___ Python tracker __

[issue15447] A file is not properly closed by webbrowser._invoke

Anton Barkovsky added the comment: The warning is printed by the file object when it closes itself in __del__: ResourceWarning: unclosed file <_io.TextIOWrapper name='/dev/null' mode='r+' encoding='UTF-8'> There isn't much to test, or is there? -- _

[issue15447] A file is not properly closed by webbrowser._invoke

Anton Barkovsky added the comment: To clarify, I discovered this when I was simply running webbrowser.open in REPL. -- ___ Python tracker ___ ___

[issue15447] A file is not properly closed by webbrowser._invoke

Ross Lagerwall added the comment: Are there any webbrowser unit tests? (this could probably use the new subprocess.DEVNULL constant in 3.3) -- nosy: +rosslagerwall ___ Python tracker _

[issue15438] Incredible issue in math.pow

Ramchandra Apte added the comment: > [+1 for removing pow from the builtins and shunting three-argument pow to the > math module in Python 500.] Me too. Anybody who uses pow with to arguments can use arg1**arg2 Anybody who uses pow with three is doing something mathematical and has most li

[issue15447] A file is not properly closed by webbrowser._invoke

R. David Murray added the comment: @Anton: That's what I was guessing. If we had a unit test in test_webbrowser that did the same thing, we'd have seen the resource warning when running the tests and fixed it. However, it looks like there aren't *any* tests for webbrowser, not even in test_

[issue12834] PyBuffer_ToContiguous() incorrect for non-contiguous arrays

Stefan Krah added the comment: Here's a patch for 3.3, which consists mostly of tests. A couple of points: o I removed the len > view->len check in PyBuffer_ToContiguous(), since the function is not documented and silently accepting output buffers that are too large seems unusual to m

[issue15447] A file is not properly closed by webbrowser._invoke

Anton Barkovsky added the comment: Adding a patch that uses subprocess.DEVNULL instead. Writing tests for webbrowser should be a separate issue, right? -- Added file: http://bugs.python.org/file26513/fileclose_devnull.patch ___ Python tracker

[issue15438] Incredible issue in math.pow

Stefan Krah added the comment: Ramchandra Apte wrote: > > [+1 for removing pow from the builtins and shunting three-argument pow to > > the math module in Python 500.] > Anybody who uses pow with three is doing something mathematical and has most > likely imported math already. Wouldn't

[issue15438] Incredible issue in math.pow

Mark Dickinson added the comment: > Wouldn't that reinforce the misconception that math is for arbitrary > precision number theoretical functions? Perhaps. We already have math.factorial, though; adding math.powmod wouldn't seem so much of a stretch. Just to be clear, I'm not seriously prop

[issue15447] A file is not properly closed by webbrowser._invoke

R. David Murray added the comment: You could do it either way. Normally we prefer to have a test along with any fix; in this case adding a test involves adding the test module as well, but it is not different in principle. If you want to work on it and prefer to have it as a separate issue

[issue15402] Correct __sizeof__ support for struct

Meador Inge added the comment: While looking this up in the C Standard (ISO/IEC 9899:TC3) I also noticed 6.3.2.3p8: """ A pointer to a function of one type may be converted to a pointer to a function of another type and back again; the result shall compare equal to the original pointer. If a

[issue14930] Make memoryview weakrefable

Richard Oudkerk added the comment: Is it possible that the use of test.support.gc_collect() in test_memoryview made the difference? -- ___ Python tracker ___ __

[issue15444] Incorrectly written contributor's names

Chris Jerdonek added the comment: To be clear on this issue's scope, I would state in a single comment a white list of which directories or individual files are being corrected (or if necessary, the rules to determine such a list, e.g. any file whose name root is "NEWS", etc). I would also r

[issue15444] Incorrectly written contributor's names

Ezio Melotti added the comment: Make sure that it's still possible to generate the pdf of the docs (with `make latex` and then `make all-pdf` in build/latex/). Latin1 should be fine, but IIRC non-latin1 will break (sorry Žiga). -- nosy: +ezio.melotti __

[issue15439] Include Misc/ACKS names into the documentation

Ezio Melotti added the comment: FWIW including Misc/ACKS in the doc will probably break the generation of the pdf version of the doc, since it contains non-latin1 characters (see msg166408). I don't think it's necessary to include the names in the doc. > I don't know how Doc ACKS is maintain

[issue15439] Include Misc/ACKS names into the documentation

Martin v. Löwis added the comment: OK, I propose to completely drop the Doc/ACKS.txt from the documentation, and replace it with the words "Many people have contributed to the Python language, the Python standard library, and the Python documentation. See Misc/ACKS in the Python source distr

[issue15437] Merge Doc/ACKS.txt names into Misc/ACKS

Martin v. Löwis added the comment: I don't think the docs should display Misc/ACKS. Instead, I propose the following wording "Many people have contributed to the Python language, the Python standard library, and the Python documentation. See Misc/ACKS in the Python source distribution for a

[issue14930] Make memoryview weakrefable

Stefan Krah added the comment: Sorry folks, I messed up the revisions when testing. This commit has nothing to do with the decreased coverage. Now I properly bisected and in r75481 mbuf_clear() and memory_clear() are still covered, but in r75484 they are not. r75484 addresses #1469629. I've go

[issue15448] utimes() functions fail with ENOSYS even when detected by configure

New submission from Richard Moseley : When building on a ASUS Eee PC 1000 running the original Xandros O/S with libc-2.7-13, the various utimes() functions are being detected as available for use, everything compiles. However, during installation of the lib-dynload libraries, the error 'Error:

[issue15443] datetime module has no support for nanoseconds

Vincenzo Ampolo added the comment: Have a look to this python dev mailing list thread too: http://mail.python.org/pipermail/python-dev/2012-July/121123.html -- ___ Python tracker _

[issue15444] Incorrectly written contributor's names

Martin v. Löwis added the comment: Indeed, PDF rendering is important. OTOH, Latex T1 does support Ž. Untested, \v{Z} should generate that character. If this doesn't work, the build process needs to be fixed. -- ___ Python tracker

[issue14930] Make memoryview weakrefable

Stefan Krah added the comment: r75484 should be b595e1ad5722. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue15445] Ability to do code injection via logging module configuration listener port.

Roundup Robot added the comment: New changeset f30b49a5072e by Vinay Sajip in branch '2.7': Issue #15445: Updated logging configuration documentation to highlight potential security risk posed by listen() in certain scenarios. http://hg.python.org/cpython/rev/f30b49a5072e New changeset e5d7d20

[issue15269] Document dircmp.left and dircmp.right

Chris Jerdonek added the comment: Thanks a lot, Eli, and for the suggestions. I would be happy to prepare a full patch. Regarding the stream argument, I think there are other changes to dircmp that would be more useful (e.g. issue 12932), but I agree that some form of your suggestion makes

[issue15444] Incorrectly written contributor's names

Ezio Melotti added the comment: > Indeed, PDF rendering is important. OTOH, Latex T1 does support Ž. I tried to put a Ž directly in an rst source and indeed the pdf has been created correctly. -- ___ Python tracker

[issue15437] Merge Doc/ACKS.txt names into Misc/ACKS

Éric Araujo added the comment: We can just use :source:`Misc/ACKS` and it will created a link to hgweb (the colored HTML page, not the raw file). -- ___ Python tracker ___

[issue15444] Incorrectly written contributor's names

Serhiy Storchaka added the comment: All names interpreted correctly except cyrillic (Alexander “Саша” Belopolsky and Марк Коренберг). I think it's just because of lack of some non-installed package (of course, Latex supports cyrillic). -- ___ Pytho

[issue15449] Optional size argument for readline()

New submission from Sworddragon : For file objects the read() function has the optional size argument to limit the data that will be read. I'm wondering why there isn't such an argument for readline(). Theoretically lines in a file could have million of characters and even much more. An option

[issue12605] Enhancements to gdb 7 debugging hooks

Antoine Pitrou added the comment: Dave, test_gdb fails consistently on the ARM buildbot: == FAIL: test_threads (test.test_gdb.PyBtTests) Verify that "py-bt" indicates threads that are waiting for the GIL --

[issue15431] Cannot build importlib.h on Windows

Changes by Antoine Pitrou : -- nosy: +kristjan.jonsson, sbt ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue15449] Optional size argument for readline()

Antoine Pitrou added the comment: Well, it does: http://docs.python.org/dev/library/io.html#io.IOBase.readline “readline(limit=-1) Read and return one line from the stream. If limit is specified, at most limit bytes will be read.” -- nosy: +pitrou ___

[issue15449] Optional size argument for readline()

Changes by Antoine Pitrou : -- resolution: -> works for me status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing

[issue15431] Cannot build importlib.h on Windows

Kristján Valur Jónsson added the comment: shouldn't be too hard to add, I'll give it a go soon. -- ___ Python tracker ___ ___ Python-

[issue15320] thread-safety issue in regrtest.main()

Chris Jerdonek added the comment: Antoine, does the latest patch look okay to you, or did you want something even more minimal (e.g. by defining and acquiring the lock directly in main)? -- ___ Python tracker ___

[issue15320] thread-safety issue in regrtest.main()

Antoine Pitrou added the comment: I would have taken the "simpler" route myself (taking the lock around the next() call), that said it looks ok as it is to me. Do other people have an opinion? -- ___ Python tracker

[issue15209] Re-raising exceptions from an expression

Tyler Crompton added the comment: As for the losing valuable debug information, much worse can be done: import sys try: x except NameError: print('An error occurred.', file=sys.stderr) sys.exit(1) This is obviously not how one should handle errors in development, but i

[issue15441] test_posixpath fails on Japanese edition of Windows

STINNER Victor added the comment: decode_filename_mbcs.patch uses the "replace" error handler to decode the filename on Windows. It should solve the issue. -- Added file: http://bugs.python.org/file26515/decode_filename_mbcs.patch ___ Python tracker

[issue15441] test_posixpath fails on Japanese edition of Windows

Martin v. Löwis added the comment: haypo: how is this meant to fix the bug? Won't it now cause a WindowsError, when a successful operation is expected? -- ___ Python tracker __

[issue15008] PEP 362 "Signature Objects" reference implementation

Benjamin Peterson added the comment: Are we going to get documentation? -- nosy: +benjamin.peterson ___ Python tracker ___ ___ Python

[issue15320] thread-safety issue in regrtest.main()

Chris Jerdonek added the comment: Thanks, Antoine. Just a note: with that other implementation I think the call to pending.close() would probably also warrant a lock since it appears close() can't be called either if a generator is already executing (granted that situation would be even rarer

[issue15402] Correct __sizeof__ support for struct

Jesús Cea Avión added the comment: So the good old "int main(void)" behaviour is "undefined" :-) -- ___ Python tracker ___ ___ Python

[issue15402] Correct __sizeof__ support for struct

Jesús Cea Avión added the comment: Talking about this, anybody has an electronic version of C Standard to share with me, or should I hunt around the dark corners of Internet? :-) -- ___ Python tracker ___

[issue7593] Computed-goto patch for RE engine

Changes by Ezio Melotti : -- versions: +Python 3.4 -Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: h

[issue15402] Correct __sizeof__ support for struct

Meador Inge added the comment: On Wed, Jul 25, 2012 at 5:38 PM, Jesús Cea Avión wrote: > So the good old "int main(void)" behaviour is "undefined" :-) Actually the C Standard says that is OK. See 5.1.2.2.1 of ISO/IEC 9899:TC3. -- ___ Python track

[issue13525] Tutorial: Example of Source Code Encoding triggers error

Changes by Ezio Melotti : -- type: -> enhancement ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue14501] Error initialising BaseManager class with 'authkey' argument of string type.

Changes by Ezio Melotti : -- nosy: +jnoller stage: -> needs patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue4712] Document pickle behavior for subclasses of dicts/lists

Changes by Ezio Melotti : -- versions: +Python 3.2, Python 3.3, Python 3.4 -Python 2.6, Python 3.0, Python 3.1 ___ Python tracker ___

[issue15320] thread-safety issue in regrtest.main()

Roundup Robot added the comment: New changeset d7a64e095930 by Antoine Pitrou in branch '3.2': Issue #15320: Make iterating the list of tests thread-safe when running tests in multiprocess mode. http://hg.python.org/cpython/rev/d7a64e095930 New changeset 43ae2a243eca by Antoine Pitrou in branc

[issue15320] thread-safety issue in regrtest.main()

Antoine Pitrou added the comment: Ok, I've committed the patch to 3.2 and 3.3. I don't really want to bother with 2.7 (it's a rare enough issue). Thank you Chris! -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed versions: -Python 2.7 _

[issue13538] Improve doc for str(bytesobject)

Changes by Ezio Melotti : -- keywords: +easy stage: -> needs patch type: -> enhancement ___ Python tracker ___ ___ Python-bugs-list

[issue15436] __sizeof__ is not documented

Raymond Hettinger added the comment: This may be CPython specific. Also, sys.getsizeof() hasn't proved to be very useful (I never see anyone use it or see it in production code). Worse, it doesn't even make sense in the case of shared-key dictionaries and whatnot. Accordingly, there is litt

[issue15436] __sizeof__ is not documented

Antoine Pitrou added the comment: sys.getsizeof() is not for production code, it's for experimenting and getting information at the command prompt. It's quite useful when you know its limitations. I'd argue that implementing __sizeof__ for user types doesn't make much sense (except C extensi

[issue15008] PEP 362 "Signature Objects" reference implementation

Yury Selivanov added the comment: Benjamin: http://bugs.python.org/issue15151 -- nosy: +yselivanov ___ Python tracker ___ ___ Python-

[issue15441] test_posixpath fails on Japanese edition of Windows

STINNER Victor added the comment: > haypo: how is this meant to fix the bug? > Won't it now cause a WindowsError, when a successful > operation is expected? Oh, I was referring to the new test proposed in the attached patch (issue15441.patch): +def test_chdir_invalid_filename(self): +

[issue15269] Document dircmp.left and dircmp.right

Chris Jerdonek added the comment: Attaching a patch to address Eli's requests (1) and (2). Since this patch merely adds documentation and tests for existing functionality, is there any reason why this cannot go into Python 3.3? Thanks. -- Added file: http://bugs.python.org/file26516/

[issue15450] Allow dircmp.subdirs to behave well under subclassing

New submission from Chris Jerdonek : Currently, the subdirs attribute of filecmp.dircmp does not respect subclassing: >>> from filecmp import dircmp >>> class MyDirCmp(dircmp): ... pass ... >>> my_dcmp = MyDirCmp('dir1', 'dir2') >>> for item in my_dcmp.subdirs.values(): ... print(type(item)

[issue14330] don't use host python, use host search paths for host compiler

Ezio Melotti added the comment: The last changeset (7955d769fdf5) caused some problem on my machine. Before the changeset I was getting: Python build finished, but the necessary bits to build these modules were not found: _bz2 _curses_curses_panel _dbm

[issue14501] Error initialising BaseManager class with 'authkey' argument of string type.

Changes by Richard Oudkerk : -- nosy: +sbt ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue15441] test_posixpath fails on Japanese edition of Windows

Atsuo Ishimoto added the comment: Here's another try: In this patch: - skip test_nonascii_abspath() test since it fails on some code pages. - Added a test to reproduce bug on latin code pages. - Use repr(filename) only if decode failed. This is more backward-compatible and does not lose any

[issue15441] test_posixpath fails on Japanese edition of Windows

Atsuo Ishimoto added the comment: martin: while os.mkdir(b'\xe7w\xf0') succeeds, but strangely enough, subsequent os.chdir(b'\xe7w\xf0') fails. This is not a bug in Python, but Windows issue. -- ___ Python tracker

[issue15451] PATH is not honored in subprocess.Popen in win32

New submission from Grissiom Gu : My system is 32 bit win7 and python is 2.7.2. Sample code is here: === import os, sys nenv = {} nenv['PATH'] = 'C:\\Windows\\System32\\;e:\\projects\\teest\\python\\exe\\' nenv['SystemRoot'] = 'C:\\Windows\\' #os.putenv('PATH', nenv['PATH']

  1   2   >