[issue13566] Array objects pickled in 3.x with protocol <=2 are unpickled incorrectly in 2.x

Changes by Serhiy Storchaka : -- nosy: +terry.reedy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue20038] Crash due to I/O in __del__

New submission from Guido van Rossum: I was writing a new Tulip example (a cache client and server, not yet public) and I noticed that when I interrupted the client with ^C I got a traceback (expected) followed by a segfault (unexpected). This is on OSX 10.8 but I don't think it is platform d

[issue20014] Makes array.array constructor accepts ascii-unicode typecode

Terry J. Reedy added the comment: This enhancement request would have been nice in 2.7.0 but it is too late for bugfix releases. Typecodes have always been shown as instances of str and still are. The doc no where suggests that unicode chars should work in 2.7 and it is not a bug that they do

[issue20015] Allow 1-character ASCII unicode where 1-character str is required

Terry J. Reedy added the comment: Victor and Stefan are correct. 2.7 is a fixed version of Python. CPython 2.7.z, z >= 1, only gets bug (and build) fixes. A 'new 2.7 version' would be 2.8, which will not happen. The fact that you propose to change the unambiguous doc shows that this is an enha

[issue20014] Makes array.array constructor accepts ascii-unicode typecode

Changes by Terry J. Reedy : -- stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue20003] Language Ref "raise" doc misssing "from None"

Changes by Terry J. Reedy : -- resolution: -> duplicate stage: -> committed/rejected status: open -> closed superseder: -> Document 'from None' in raise statement doc. type: -> enhancement ___ Python tracker __

[issue19998] Python 2.7.6 fails to build _ctypes on GCC 2.x toolchain

Terry J. Reedy added the comment: I believe an upstream change will be automatically picked up by any subsequent CPython release without an explicit tracker patch. -- nosy: +terry.reedy resolution: -> later status: open -> closed ___ Python tracker

[issue1100942] Add datetime.time.strptime and datetime.date.strptime

Maciej Szulik added the comment: I'm attaching merged and fixed patch (issue1100942_full.patch). Though during testing I found one issue with the patch: during checking for time part in date class I'm using (in _datetimemodule.c->date_strptime) DATE_GET_HOUR etc, but when given time parts are

[issue19967] asyncio: remove _TracebackLogger

Changes by STINNER Victor : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue19967] asyncio: remove _TracebackLogger

Roundup Robot added the comment: New changeset 06ed1691efdc by Victor Stinner in branch 'default': Issue #19967: Defer the formating of the traceback in asyncio.Future destructor http://hg.python.org/cpython/rev/06ed1691efdc -- ___ Python tracker

[issue19995] hex() and %x, oct() and %o do not behave the same

Terry J. Reedy added the comment: It seems to me that anything that is an 'integer' that can be turned into an int without loss of information (has .__index__) is logically a 'number' that can be turned into an int possibly with loss of information (has .__int__). So perhaps one of the follow

[issue19967] asyncio: remove _TracebackLogger

Guido van Rossum added the comment: Victor, can you commit the fix (with my suggested improvement)? -- ___ Python tracker ___ ___ Pyth

[issue20032] asyncio.Future.set_exception() creates a reference cycle

STINNER Victor added the comment: "The cycle will be cleaned up (and the message printed) when the garbage collector runs next." Oh, ok. Using the following task, the object is correctly deleted. --- @asyncio.coroutine def idle(): while 1: gc.collect() yield from asyncio.slee

[issue20032] asyncio.Future.set_exception() creates a reference cycle

Changes by STINNER Victor : -- resolution: -> invalid status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue20032] asyncio.Future.set_exception() creates a reference cycle

Guido van Rossum added the comment: The only reasonable place to break the cycle seems to be the frame containing the set_exception() call -- but that could be app code. Looking again at what the patch actually does I think it is too big a hammer anyway -- it would break debugging tools that p

[issue20032] asyncio.Future.set_exception() creates a reference cycle

Antoine Pitrou added the comment: > Maybe it's time to look into > http://code.google.com/p/tulip/issues/detail?id=42 ? (It proposes to > run gc.collect() occasionally when the loop is idle.) Is it possible to break the cycle instead? Or is the graph of references too complex for that?

[issue20029] asyncio.SubprocessProtocol is missing

Guido van Rossum added the comment: There's one issue left: the docs need to document BaseProtocol. -- assignee: -> haypo stage: -> needs patch ___ Python tracker ___ _

[issue20032] asyncio.Future.set_exception() creates a reference cycle

Guido van Rossum added the comment: The cycle will be cleaned up (and the message printed) when the garbage collector runs next. Your demo doesn't do anything else, so it never allocates memory, so it never runs gc.collect(). But that's only because it's a toy program. Maybe it's time to look in

[issue20037] Calling traceback.format_exception() during Pyhon shutdown does crash Python

STINNER Victor added the comment: Begin of the C traceback: #0 0x004bf70a in PyModule_GetState (m=0x0) at Objects/moduleobject.c:292 #1 0x006373b6 in textiowrapper_init (self=0x71073790, args=(<_io.BufferedReader at remote 0x7fffefa094b8>, 'utf-8'), kwds={'line_buffe

[issue20037] Calling traceback.format_exception() during Pyhon shutdown does crash Python

New submission from STINNER Victor: Attached crash.py script does crash Python. Python traceback on the crash: (gdb) py-bt Traceback (most recent call first): File "/home/haypo/prog/python/default/Lib/tokenize.py", line 431, in open text = TextIOWrapper(buffer, encoding, line_buffering=Tr

[issue20029] asyncio.SubprocessProtocol is missing

Roundup Robot added the comment: New changeset 0a135e790ce5 by Guido van Rossum in branch 'default': asyncio: Export all abstract protocol and transport classes. Fixes issue #20029. http://hg.python.org/cpython/rev/0a135e790ce5 -- nosy: +python-dev __

[issue20032] asyncio.Future.set_exception() creates a reference cycle

STINNER Victor added the comment: > Do you have an example of code that behaves differently with this patch? I > can't find any. I didn't check in the Python standard library, but the reference cycle is obvious, and I hate such issue. It introduces tricky issues like memory leaks. Here is an

[issue20029] asyncio.SubprocessProtocol is missing

Guido van Rossum added the comment: I propose that we fix the code. There are also some documented Transport classes that aren't listed in __all__. I'll submit the fix. -- ___ Python tracker

[issue20032] asyncio.Future.set_exception() creates a reference cycle

Antoine Pitrou added the comment: +self._loop.call_soon(traceback.clear_frames, + self._exception.__traceback__) This will keep the traceback alive until called by the event loop, even if self._exception is cleared in the meantime... --

[issue20029] asyncio.SubprocessProtocol is missing

Changes by Antoine Pitrou : -- nosy: +gvanrossum, haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue19717] resolve() fails when the path doesn't exist

Antoine Pitrou added the comment: Well, given the diversity of possible behaviours, it starts to seem like it should maybe be discussed on python-dev. -- ___ Python tracker ___

[issue20036] Running same doctests not possible on both py3 and py2

R. David Murray added the comment: No problem. It's not necessarily *obvious* what one needs to do to make this work, so missing it isn't too surprising. -- ___ Python tracker

[issue20036] Running same doctests not possible on both py3 and py2

Maries Ionel Cristian added the comment: Oooops, sorry. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue20036] Running same doctests not possible on both py3 and py2

R. David Murray added the comment: This has already been addressed in issue 7490. -- nosy: +r.david.murray resolution: -> duplicate stage: -> committed/rejected status: open -> closed superseder: -> IGNORE_EXCEPTION_DETAIL should ignore the module name ___

[issue20036] Running same doctests not possible on both py3 and py2

Changes by Maries Ionel Cristian : Added file: http://bugs.python.org/file33237/tete.rst ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue20036] Running same doctests not possible on both py3 and py2

New submission from Maries Ionel Cristian: One of these doesn't work depending on how you write the exception name. python3 -mdoctest src/tete.rst python -mdoctest src/tete.rst One cannot put an ellipsis in the exception name so you see how this is a problem. -- components: De

[issue20035] Suppress 'os.environ was modified' warning on Tcl/Tk tests

Zachary Ware added the comment: I like that idea, though I'm a bit wary of messing around is sys.modules. Is there another way to unload a module that I'm not aware of? Here's a new patch that does that. -- Added file: http://bugs.python.org/file33235/suppress_environ_warning.v2.diff

[issue20035] Suppress 'os.environ was modified' warning on Tcl/Tk tests

Changes by R. David Murray : -- nosy: +r.david.murray ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

[issue20035] Suppress 'os.environ was modified' warning on Tcl/Tk tests

Serhiy Storchaka added the comment: This looks fragile. What if some test will import tkinter after other test "unfix" the environment? I suggest unload the tkinter._fix module in unfix_environ(). Then next import should implicitly fix the environment. And explicit fix_environ() will be not ne

[issue20027] Fixed support for Indian locales

Changes by Serhiy Storchaka : Removed file: http://bugs.python.org/file33231/locale_devanagari_2.patch ___ Python tracker ___ ___ Python-bugs-

[issue20027] Fixed support for Indian locales

Serhiy Storchaka added the comment: Updated patch to tip. The makelocalalias.py script now corrects the non-standard locale names. -- Added file: http://bugs.python.org/file33234/locale_devanagari_3.patch ___ Python tracker

[issue20032] asyncio.Future.set_exception() creates a reference cycle

Guido van Rossum added the comment: Do you have an example of code that behaves differently with this patch? I can't find any. -- ___ Python tracker ___ ___

[issue20034] Update locale alias table

Roundup Robot added the comment: New changeset 72e68af9e2fa by Serhiy Storchaka in branch 'default': Issue #20034: Updated alias mapping to most recent locale.alias file http://hg.python.org/cpython/rev/72e68af9e2fa -- ___ Python tracker

[issue20035] Suppress 'os.environ was modified' warning on Tcl/Tk tests

New submission from Zachary Ware: The attached patch refactors tkinter._fix's main logic into a function called 'fix_environ' which is called unconditionally on import, and adds a function 'unfix_environ' to undo the effects of fix_environ. fix/unfix_environ are then used in all test files th

[issue20034] Update locale alias table

Roundup Robot added the comment: New changeset 81f8375e60ce by Serhiy Storchaka in branch '2.7': Issue #20034: Updated alias mapping to most recent locale.alias file http://hg.python.org/cpython/rev/81f8375e60ce New changeset ed62c4c70c4d by Serhiy Storchaka in branch '3.3': Issue #20034: Update

[issue20034] Update locale alias table

Serhiy Storchaka added the comment: Thanks for your review, Marc-Andre. -- assignee: -> serhiy.storchaka resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker __

[issue20027] Fixed support for Indian locales

Marc-Andre Lemburg added the comment: On 20.12.2013 16:24, Serhiy Storchaka wrote: > > Serhiy Storchaka added the comment: > >> Well, yes, but only because you are removing the @-modifiers. I don't >> think that's correct, since e.g. the string formatting used for >> numbers is different with t

[issue20034] Update locale alias table

Marc-Andre Lemburg added the comment: On 20.12.2013 16:12, Serhiy Storchaka wrote: > > Serhiy Storchaka added the comment: > >> Looks good. > > Should these patch be applied only to 3.4 or to all maintained > releases? I suppose the later, because alias table which is not > conform recent sy

[issue20027] Fixed support for Indian locales

Serhiy Storchaka added the comment: > Well, yes, but only because you are removing the @-modifiers. I don't > think that's correct, since e.g. the string formatting used for > numbers is different with the modifier. All the @-modifiers except euro are applied to the locale, not the encoding. An

[issue20034] Update locale alias table

Serhiy Storchaka added the comment: > Looks good. Should these patch be applied only to 3.4 or to all maintained releases? I suppose the later, because alias table which is not conform recent systems configuration is a bug. > BTW, regarding the devanagari cases: This patch only updates the d

[issue20027] Fixed support for Indian locales

Marc-Andre Lemburg added the comment: On 20.12.2013 15:55, Serhiy Storchaka wrote: > > After applying the patch Python supports all ks_IN and sd_IN locales. Well, yes, but only because you are removing the @-modifiers. I don't think that's correct, since e.g. the string formatting used for numb

[issue20027] Fixed support for Indian locales

Serhiy Storchaka added the comment: Ubuntu 12.04 supports Kashmiri and Sindhi locales (requires language-pack-sd-base and language-pack-sd-base packages). $ locale -a ... ks_IN ks_IN@devanagari ks_IN.utf8 ks_IN.utf8@devanagari ... sd_IN sd_IN@devanagari sd_IN.utf8 sd_IN.utf8@devanagari ... Cur

[issue19946] Handle a non-importable __main__ in multiprocessing

Nick Coghlan added the comment: Now passing on all the stable buildbots (the two red Windows bots are for other issues, such as issue 15599 for the threaded import test failure) -- status: pending -> closed ___ Python tracker

[issue15599] test_threaded_import fails sporadically on Windows and FreeBSD

Nick Coghlan added the comment: Another recent instance of the parallel meta path failure: http://buildbot.python.org/all/builders/x86%20Windows7%203.x/builds/7740/steps/test/logs/stdio -- keywords: +buildbot -patch nosy: +ncoghlan ___ Python tracker

[issue20034] Update locale alias table

Berker Peksag added the comment: See also issue 16555. -- nosy: +berker.peksag ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue20027] Fixed support for Indian locales

Marc-Andre Lemburg added the comment: On 20.12.2013 12:19, Serhiy Storchaka wrote: > > Added file: http://bugs.python.org/file33231/locale_devanagari_2.patch See my message on issue20034: There is some recent activity in glibc related to these. Here's a patch that adds the sd_IN@devanagari lo

[issue20034] Update locale alias table

Marc-Andre Lemburg added the comment: On 20.12.2013 12:36, Serhiy Storchaka wrote: > > Proposed patch updates locale alias table to most recent locale.alias file > (from X.org 7.7 distribution). Looks good. BTW, regarding the devanagari cases: There is some recent activity in glibc related t

[issue19736] posixmodule.c: Add flags for statvfs.f_flag to constant list

Changes by Matthias Klose : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue19946] Handle a non-importable __main__ in multiprocessing

Nick Coghlan added the comment: Pending a clean bill of health from the stable buildbots :) -- status: open -> pending ___ Python tracker ___

[issue19946] Handle a non-importable __main__ in multiprocessing

Roundup Robot added the comment: New changeset 00d09afb57ca by Nick Coghlan in branch 'default': Issue #19946: use public API for multiprocessing start methods http://hg.python.org/cpython/rev/00d09afb57ca -- ___ Python tracker

[issue20034] Update locale alias table

New submission from Serhiy Storchaka: Proposed patch updates locale alias table to most recent locale.alias file (from X.org 7.7 distribution). -- components: Library (Lib) files: locale_aliases_77.patch keywords: patch messages: 206676 nosy: lemburg, loewis, serhiy.storchaka priority:

[issue20027] Fixed support for Indian locales

Changes by Serhiy Storchaka : Removed file: http://bugs.python.org/file33219/locale_devanagari.patch ___ Python tracker ___ ___ Python-bugs-li

[issue20027] Fixed support for Indian locales

Changes by Serhiy Storchaka : Added file: http://bugs.python.org/file33231/locale_devanagari_2.patch ___ Python tracker ___ ___ Python-bugs-li

[issue20033] Fix makelocalealias.py for Python 3

New submission from Serhiy Storchaka: When Tools/i18n/makelocalealias.py was ported to Python 3 some things were not fixed. 1. locale.alias is opened as binary file in Python 2, but as text file (with locale encoding) in Python 3. This can cause fail when the script runs in UTF-8 locale becau

[issue20032] asyncio.Future.set_exception() creates a reference cycle

STINNER Victor added the comment: asyncio_break_ref_cycle.patch does not fix the issue on Python 3.3 (for Tulip). -- ___ Python tracker ___ __

[issue20032] asyncio.Future.set_exception() creates a reference cycle

New submission from STINNER Victor: asyncio.Future.set_exception(exc) sets the exception attribute to exc, but exc.__traceback__ refers to frames and the current frame probably referes to the future instance. Tell me if I'm wrong, but it looks like a reference cycle: fut -- fut.exception --> e

[issue19967] asyncio: remove _TracebackLogger

STINNER Victor added the comment: > I think this patch is bad and should be reverted. It always calls > traceback.format_exception() which is an expensive operation, while the > _TracebackLogger takes care to call it only when necessary. Oh, I didn't notice that, and I agree that the new code

[issue20031] unittest.TextTestRunner missing run() documentation.

Changes by Ezio Melotti : -- keywords: +easy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue20030] unittest.TestLoader.discover return value incorrectly documented.

Changes by Ezio Melotti : -- keywords: +easy nosy: +ezio.melotti, michael.foord stage: -> needs patch type: -> enhancement versions: +Python 3.4 ___ Python tracker ___

[issue20031] unittest.TextTestRunner missing run() documentation.

Changes by Ezio Melotti : -- nosy: +ezio.melotti, michael.foord stage: -> needs patch type: -> enhancement versions: +Python 3.4 ___ Python tracker ___

[issue20031] unittest.TextTestRunner missing run() documentation.

New submission from Arnaut Billings: Here: http://docs.python.org/3/library/unittest.html 1) unittest.TextTestRunner is missing documentation for its public run method. 2) There are references to the TestRunner class sprinkled through out the above page, yet no link or documentation as to what

[issue20030] unittest.TestLoader.discover return value incorrectly documented.

New submission from Arnaut Billings: Here: http://docs.python.org/3/library/unittest.html#unittest.TestLoader.discover it states that "Find and return all test modules ..." This implies that in order to get a test suite, one has to iterate over the return value of unittest.TestLoader.discover

[issue19927] Path-based loaders lack a meaningful __eq__() implementation.

Eric Snow added the comment: Unless there are objections, I'll commit this in the next day or two. -- ___ Python tracker ___ ___ Pytho