[issue14428] Implementation of the PEP 418

Charles-François Natali added the comment: Tiny review. Two more details: - since it's relatively straightforward to cache the last value returned using a static variable, it might be interesting to use this to make sure that the values returned are indeed monotonic - I'm not a native speaker

[issue14386] Expose dictproxy as a public type

Guido van Rossum added the comment: Since it has to go *somewhere*, let's put it in the types module. It has a variety of other types that are used in the implementation of classes and functions and related things. -- ___ Python tracker

[issue14408] Support the load_tests protocol in the stdlib tests

Michael Foord added the comment: Yes, it would be preferable if unittest could load the set of test classes for each of these test modules without *requiring* a load_tests function. Each test module will need looking at to see if the standard set of test classes exported by the module is the

[issue14432] Bug in generator if the generator in created in a C thread

New submission from STINNER Victor : We have a crash in our product when tracing is enabled by sys.settrace() and threading.settrace(). If a Python generator is created in a C thread, calling the generator later in another thread may crash if Python tracing is enabled. - the C thread calls PyGI

[issue14408] Support the load_tests protocol in the stdlib tests

R. David Murray added the comment: Your presumption is probably correct, however if that is the premise of the patch it is incorrect in detail, since we've already fixed test_queue specifically to be runnable with -m unittest without adding a load_tests. I haven't looked at the other modules

[issue14432] Bug in generator if the generator in created in a C thread

Ross Lagerwall added the comment: Here's the patch ;-) -- keywords: +patch nosy: +rosslagerwall Added file: http://bugs.python.org/file25055/generator.patch ___ Python tracker _

[issue7511] msvc9compiler.py: ValueError when trying to compile with VC Express

Martin v. Löwis added the comment: Victor, can you apply this patch and report that it works. In particular, if it does *not* work, can you please report the exact way of failing? (if you can, please also try to investigate why it fails). -- ___ Py

[issue14432] Bug in generator if the generator in created in a C thread

Nick Coghlan added the comment: The proposed fix sounds reasonable to me. Would it be possible to work something into test_capi to actually test it? -- nosy: +ncoghlan ___ Python tracker _

[issue14322] More test coverage for hmac

Changes by Vijay Majagaonkar : -- nosy: +Vijay.Majagaonkar ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue14432] Bug in generator if the generator in created in a C thread

Nick Coghlan added the comment: It may not even have to specifically test the crash - any operation that accessed the tstate on the frame and could be shown to be accessing the wrong thread state when called from another thread could demonstrate the problem. -- __

[issue14408] Support the load_tests protocol in the stdlib tests

Éric Araujo added the comment: > Of course this would remove the possibility to run things like “../../python > test_shutil.py” I was wrong: we would just have the usual two-liner invoking unittest.main. What would be broken is running via regrtest if we remove test_main functions (IIRC); t

[issue14408] Support ./python -m unittest in the stdlib tests

Changes by Éric Araujo : -- title: Support the load_tests protocol in the stdlib tests -> Support ./python -m unittest in the stdlib tests ___ Python tracker ___ ___

[issue14408] Support ./python -m unittest in the stdlib tests

R. David Murray added the comment: The test_main functions can be converted to use unittest discovery, though. That's what I did for test_email. -- ___ Python tracker ___

[issue14423] Getting the starting date of iso week from a week number and a year.

Esben Agerbæk Black added the comment: Patch updated with sanity checks. -- Added file: http://bugs.python.org/file25056/isodates.patch ___ Python tracker ___ __

[issue14408] Support ./python -m unittest in the stdlib tests

Michael Foord added the comment: Test discovery is only needed for finding tests in directories of tests - for a single test module the standard test loader should work fine. -- ___ Python tracker ___

[issue12643] code.InteractiveConsole ignores sys.excepthook

Changes by Florent Xicluna : -- nosy: +flox ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue14408] Support ./python -m unittest in the stdlib tests

R. David Murray added the comment: Right. What I meant to say was "test_main can be converted to use normal unittest test loading". test_email is not an example of that, since it does use test discovery, but is a good example of a test collection that works with both regrtest and unittest w

[issue14423] Getting the starting date of iso week from a week number and a year.

Changes by R. David Murray : -- keywords: +needs review nosy: +belopolsky stage: -> patch review versions: -Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.4 ___ Python tracker __

[issue7511] msvc9compiler.py: ValueError when trying to compile with VC Express

Victor Lin added the comment: Oddly, can't reproduce the problem anymore. I try to install win7 on virtual machine, but it works as well. I think the issue might caused by something else... not sure, so strange :S Will look into detail once I encounter this issue again. -- _

[issue14409] IDLE does not execute any commands (command prompt works fine!)

Ankit Agrawal added the comment: Another cfg file from the original .idlerc folder -- Added file: http://bugs.python.org/file25058/config-main.cfg ___ Python tracker ___ ___

[issue14409] IDLE does not execute any commands (command prompt works fine!)

Ankit Agrawal added the comment: Please find attached, the original .cfg files that I was found in my idlerc folder. I hope this proves helpful. If you need any other information I'd be glad to help. -- status: pending -> open Added file: http://bugs.python.org/file25057/config-exten

[issue14423] Getting the starting date of iso week from a week number and a year.

Esben Agerbæk Black added the comment: Patch updated with tests and documentation -- Added file: http://bugs.python.org/file25059/isodates.patch ___ Python tracker ___ _

[issue14433] Python 3 interpreter crash with memoryview and os.fdopen

New submission from Alexis Daboville : Hi, I was "playing" with memoryviews when I found this behaviour, launch the Python shell, and then enter the following: >>> import os >>> memoryview(os.fdopen(0)) A TypeError "cannot make memory view because object does not have the buffer interface" i

[issue14432] Bug in generator if the generator in created in a C thread

Changes by Andrew Svetlov : -- nosy: +asvetlov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue14433] Python 3 interpreter crash with memoryview and os.fdopen

Charles-François Natali added the comment: Hello, This has actually nothing to do with memoryview: """ >>> import os [67212 refs] >>> stdin = os.fdopen(0) [67234 refs] >>> del stdin __main__:1: ResourceWarning: unclosed file <_io.TextIOWrapper name=0 mode='r' encoding='UTF-8'> [67260 refs] >>

[issue14433] Python 3 interpreter crash with memoryview and os.fdopen

Brian Curtin added the comment: > So it's not an issue, try calling memoryview(fdopen( 0,1,2>) and it'll work. This is exactly why it's an issue. Python should not crash. -- nosy: +brian.curtin status: closed -> open ___ Python tracker

[issue14409] IDLE: not executing commands from shell, error with default keybinding for Return

Roger Serwy added the comment: Thank you for the configuration files. It helped with finding the bug. The default key bindings in configHandler.py is incorrect for <> which caused the problem Ankit experienced. This problem affects the 2.7 and 3.3 series. Attached is a patch against 3.3 (a

[issue14433] Python 3 interpreter crash with memoryview and os.fdopen

R. David Murray added the comment: To make this a little clearer, here's an even simpler example: >>> import os >>> os.fdopen(0) <_io.TextIOWrapper name=0 mode='r' encoding='UTF-8'> >>> 1 __main__:1: ResourceWarning: unclosed file <_io.TextIOWrapper name=0 mode='r' encoding='UTF-8'> 1

[issue14433] Python 3 interpreter crash with memoryview and os.fdopen

Alexis Daboville added the comment: First, thank you all for the explanations (sorry for the misleading title about the memoryview, should I rename it?). > @Brian: this isn't a crash. It is completely equivalent to pressing D > at the interactive interpreter prompt. Not exactly, at least on

[issue14433] Python 3 interpreter crash with memoryview and os.fdopen

Brian Curtin added the comment: Maybe it's a different reason, but some part of something about this crashes on Windows. "python.exe has stopped working" is a crash dialog. -- ___ Python tracker _

[issue14433] Python 3 interpreter crash with memoryview and os.fdopen

R. David Murray added the comment: Hmm. And D isn't how you shut down the interpreter on Windows, is it? So maybe there is a Windows-specific bug here after all. Or do you get that same dialog if you do the Windows equivalent of D in a shell window (is that different from a CMD window, or

[issue14409] IDLE: not executing commands from shell, error with default keybinding for Return

Ned Deily added the comment: Roger, I notice that the line your patch modifies in configHandler.py has been unchanged for years and is the same in older Python versions. My impression from Ankit's description is that this is a new problem. What's different or am I misunderstanding something

[issue14386] Expose dictproxy as a public type

Raymond Hettinger added the comment: [GvR] > Since it has to go *somewhere*, let's put it > in the types module. It has a variety of other > types that are used in the implementation of > classes and functions and related things. +1 -- ___ Pytho

[issue14204] Support for the NPN extension to TLS/SSL

Changes by Marcelo Fernández : -- nosy: +marcelo_fernandez ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue14409] IDLE: not executing commands from shell, error with default keybinding for Return

Roger Serwy added the comment: Ned, the buggy default keybinding for <> requires that Key-Return and then Key-KP_Enter be pressed before the virtual event triggers. This happens because both key events are present in a single string. The correct behavior requires each key event be listed in a

[issue2090] __import__ with fromlist=

Changes by Éric Araujo : -- versions: +Python 3.3 -Python 3.1 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue14408] Support ./python -m unittest in the stdlib tests

Matt Joiner added the comment: Michael: The thread setup and cleanup is not required, AFAICT. You are also correct in that these particular test modules do not run correctly without modification (although test_queue does now that the bug I reported there was fixed). Sorry by predicated, I me

[issue14434] Tutorial link in "help()" in 3.2.2

New submission from Bill Winslow : I installed "python3" to get into a good scripting language. I ran "python3" and it said type "help". I did and it said type "help()" for interactive help, or "help(object)" for specific help. Just looking to get started, I did the former, where the message d

[issue14386] Expose dictproxy as a public type

poq added the comment: It is exposed as types.DictProxyType in Python 2... -- nosy: +poq ___ Python tracker ___ ___ Python-bugs-list