[issue23655] Memory corruption using pickle over pipe to subprocess

New submission from John Nagle: I'm porting a large, working system from Python 2 to Python 3, using "six", so the same code works with both. One part of the system works a lot like the multiprocessing module, but predates it. It launches child processes with "Popen" and talks to them using "p

[issue23051] multiprocessing.pool methods imap()[_unordered()] deadlock

Serhiy Storchaka added the comment: Thank you for your contribution Alon and Davin. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue23051] multiprocessing.pool methods imap()[_unordered()] deadlock

Roundup Robot added the comment: New changeset 525ccfcc55f7 by Serhiy Storchaka in branch '3.4': Issue #23051: multiprocessing.Pool methods imap() and imap_unordered() now https://hg.python.org/cpython/rev/525ccfcc55f7 New changeset 7891d084a9ad by Serhiy Storchaka in branch 'default': Issue #23

[issue22852] urllib.parse wrongly strips empty #fragment

Changes by Demian Brecht : -- stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

[issue2211] Cookie.Morsel interface needs update

Changes by Demian Brecht : Added file: http://bugs.python.org/file38466/issue2211_3.patch ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue23566] RFE: faulthandler.register() should support file descriptors

Wei Wu added the comment: Or we could reuse the file created by filename in subprocess? if filename: file = open(filename, "wb") if use_fd: file = file.fileno() else: file = None In this case, we need to pass two arguments(both filename and a bool use_fd) to check_xxx funct

[issue23639] Not documented special names

Martin Panter added the comment: Some of these that I believe are at least partially documented, so could be added to the index. But the index for these is not very good anyway, because they are listed in a funny (ASCII-betical?) order in a special section called “symbols”, rather than alphabe

[issue23574] datetime: support leap seconds

Akira Li added the comment: POSIX timestamp doesn't count (literally) past/future leap seconds. It allows to find out that the timestamp 2**31-1 corresponds to 2038-01-19T03:14:07Z (UTC) regardless of how many leap seconds will occur before 2038: >>> from datetime import datetime, timedelta

[issue23051] multiprocessing.pool methods imap()[_unordered()] deadlock

Davin Potts added the comment: After pondering it for two days and coming back to it with hopefully "fresh eyes", I believe that changing the for-loop to a while-loop is not overall easier to understand -- I would lean towards keeping the for-loop. I do think the change to the while-loop very

[issue23605] Use the new os.scandir() function in os.walk()

Ben Hoyt added the comment: Thanks, Victor. I haven't quite grokked all the changes here -- it's gotten somewhat more complicated with the scandir_it and manual next() call -- but I ran some benchmarks (via a hacked version of my scandir project's benchmark.py). The results were surprising, a

[issue23081] Document PySequence_List(o) as equivalent to list(o)

Berker Peksag added the comment: Thanks for the report and the patch, Lars. -- resolution: -> fixed stage: -> resolved status: open -> closed versions: +Python 3.4 ___ Python tracker _

[issue23081] Document PySequence_List(o) as equivalent to list(o)

Roundup Robot added the comment: New changeset e31e987207ab by Berker Peksag in branch '3.4': Issue #23081: Document that PySequence_List also accepts iterables. https://hg.python.org/cpython/rev/e31e987207ab New changeset eb4a0048978c by Berker Peksag in branch 'default': Issue #23081: Document

[issue22852] urllib.parse wrongly strips empty #fragment

Martin Panter added the comment: There have been a few recent bug reports (Issue 23505, Issue 23636) that may be solved by the has_netloc proposal. So I am posting a patch implementing it. The changes were a bit more involved than I anticipated, but should still be usable. I reused some of Sti

[issue17403] Robotparser fails to parse some robots.txt

Berker Peksag added the comment: Yes, this doesn't look like a security issue to me. Too late for 3.2. Closing this as "fixed". -- nosy: +berker.peksag resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: -Python 3.2 __

[issue22154] ZipFile.open context manager support

Berker Peksag added the comment: Thanks for the patch, Mike. -- nosy: +berker.peksag resolution: -> fixed stage: needs patch -> resolved status: open -> closed type: behavior -> enhancement versions: +Python 3.4 ___ Python tracker

[issue22154] ZipFile.open context manager support

Roundup Robot added the comment: New changeset b6fdf8c7a74d by Berker Peksag in branch '3.4': Issue #22154: Add an example to show context management protocol support of ZipFile.open(). https://hg.python.org/cpython/rev/b6fdf8c7a74d New changeset 390a2f4dfd4a by Berker Peksag in branch 'default

[issue17403] Robotparser fails to parse some robots.txt

Martin Panter added the comment: Perhaps it’s too late to modify the 3.2 branch now? IMO the change made for this bug abuses the behaviour of urlunparse() removing empty query strings; see Issue 22852 where I proposed to stop it doing that. -- nosy: +vadmium __

[issue9253] argparse: optional subparsers

Changes by BJ Dierkes : -- nosy: +derks ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/

[issue23138] cookiejar parses cookie value as int with empty name-value pair and Expires

Changes by Demian Brecht : Added file: http://bugs.python.org/file38464/issue23138_2.patch ___ Python tracker ___ ___ Python-bugs-list mailing

[issue17797] Visual C++ 11.0 reports fileno(stdin) == 0 for non-console program

Steve Dower added the comment: There's not much point putting this into 3.5 anymore, as we are going to break pre-VS2015 builds completely sooner or later (too many changes to the CRT that we can't just work around with #ifdefs - and too much opposition to having code purely to support unsuppo

[issue23654] infinite loop in faulthandler._stack_overflow

Changes by Berker Peksag : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.

[issue23654] infinite loop in faulthandler._stack_overflow

New submission from Matt Frank: When the faulthandler module is compiled at -O3 (the default for non-debug builds) with a compiler that does tailcall optimization the Modules/faulthandler.c:stack_overflow() function may become an infinite loop that does not expand the stack. This puts the int

[issue17797] Visual C++ 11.0 reports fileno(stdin) == 0 for non-console program

Jean-Charles Lefebvre added the comment: Oops, mistyping, #ifdef test would be: #if defined(MS_WINDOWS) && defined(HAVE_FSTAT) && defined(_MSC_VER) && _MSC_VER >= 1700 && _MSC_VER < 1900 -- ___ Python tracker ___

[issue17797] Visual C++ 11.0 reports fileno(stdin) == 0 for non-console program

Jean-Charles Lefebvre added the comment: Hi all, a small update to confirm this issue with version 3.5.0a2 embedded in a native C++ GUI application, having everything built with VS2013 SP4. Same execution flow as described by Mateusz in msg198689. I've modified Python/pylifecycle.c file accord

[issue23649] tarfile not re-entrant for multi-threading

Srdjan Grubor added the comment: The whole lib still needs the threading locks added but the patch submitted should fix things for people that do the locking from their code. -- ___ Python tracker

[issue23649] tarfile not re-entrant for multi-threading

Srdjan Grubor added the comment: Patch for the multithreaded expansion of files and use of makedirs. -- keywords: +patch Added file: http://bugs.python.org/file38462/mutithreading_tarfile.patch ___ Python tracker _

[issue23647] imaplib.py MAXLINE value is too low for gmail

R. David Murray added the comment: Sorry, I was being a facetious, but despite the smiley that wasn't clear. I *have* run into a number of cases where gmail violates the standard, but I wasn't really serious about this case. -- ___ Python tracker

[issue23653] Make inspect._empty test to False

New submission from Nathan West: A common Python idiom is to test objects by value in an if. This includes container emptiness and regular expression matches, or using 'or' to specify a default value: if my_list: # list isn't empty if regex.match(string): # string match

[issue23649] tarfile not re-entrant for multi-threading

Srdjan Grubor added the comment: After some thinking, for the makedirs it should only need makedirs(exist_ok=True) -- ___ Python tracker ___

[issue23644] g++ module compile fails with ‘_Atomic’ does not name a type

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue23652] ifdef uses of EPOLLxxx macros so we can compile on systems that don't have them

Changes by Ned Deily : -- nosy: +neologix ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.o

[issue23647] imaplib.py MAXLINE value is too low for gmail

Arnt Gulbrandsen added the comment: The RFC in question is 2683, which isn't a standard, it's just advice. What gmail breaks is the expectation that mailboxes and seach results are smallish. If you run a python script on gmail and it runs a search, the result can be a great deal bigger than th

[issue23652] ifdef uses of EPOLLxxx macros so we can compile on systems that don't have them

Changes by Matt Frank : -- type: -> compile error ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue23652] ifdef uses of EPOLLxxx macros so we can compile on systems that don't have them

New submission from Matt Frank: With the LSB (Linux Standard Base) headers for libc Modules/selectmodule.c fails to compile because we have code that uses EPOLLRDNORM, EPOLLRDBAND, EPOLLWRNORM and EPOLLMSG without first checking that they are defined. The patch wraps the five uses of PyModule_

[issue23646] PEP 475: handle EINTR in the time module, retry sleep()

STINNER Victor added the comment: Le jeudi 12 mars 2015, Charles-François Natali a écrit : > > As for the change to select/poll/etc, IIRC Guido was opposed to it, > that's why I didn't update them. > Wait what? can you elaborate? I'm not aware of that. -- _

[issue23635] Python won't install correctly.

Alex Zhang added the comment: Never mind, I used ccleaner and revo uninstaller to delete traces, then reinstalled using the msi. Thanks for help, it's all good now! -- resolution: -> fixed status: open -> closed ___ Python tracker

[issue23641] Got rid of bad dunder names

Serhiy Storchaka added the comment: Committed all except changes to multiprocessing.sharedctypes (remove __getslice__ and __setslice__) and unittest.mock (remove __div__, add __getnewargs_ex__). -- ___ Python tracker

[issue23641] Got rid of bad dunder names

Roundup Robot added the comment: New changeset 7522bb14e36a by Serhiy Storchaka in branch '3.4': Issue #23641: Cleaned out legacy dunder names from tests and docs. https://hg.python.org/cpython/rev/7522bb14e36a New changeset 9332a545ad85 by Serhiy Storchaka in branch 'default': Issue #23641: Cle

[issue23650] xml.etree.ElementTreee.write can't parse its own output

Ned Deily added the comment: This is a duplicate of Issue5166. Note that in your example, you are not serializing valid XML 1.0: \x1b (ESC) is not a valid XML character, it has to be escaped and, as the discussion in Issue5166 points out, etree does not automatically do that for you. ---

[issue23641] Got rid of bad dunder names

Berker Peksag added the comment: > Do you want first commit the patch in issue23581 Berker? I just committed it. Thanks for the review :) -- ___ Python tracker ___ _

[issue23650] xml.etree.ElementTreee.write can't parse its own output

François-Michel L'Heureux added the comment: Updated file where copy/pasting works. -- Added file: http://bugs.python.org/file38460/python_xml_builder_bug.py ___ Python tracker _

[issue23641] Got rid of bad dunder names

Serhiy Storchaka added the comment: Do you want first commit the patch in issue23581 Berker? -- ___ Python tracker ___ ___ Python-bugs

[issue23650] xml.etree.ElementTreee.write can't parse its own output

Changes by François-Michel L'Heureux : Removed file: http://bugs.python.org/file38459/python_xml_builder_bug.py ___ Python tracker ___ ___ Pyt

[issue23651] Typo in argparse allow_abrev

Berker Peksag added the comment: Good catch, Nathan. Thanks! -- nosy: +berker.peksag resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker ___ _

[issue23651] Typo in argparse allow_abrev

Roundup Robot added the comment: New changeset 8411ae359c98 by Berker Peksag in branch 'default': Issue #23651: Fix typo in allow_abbrev docs. https://hg.python.org/cpython/rev/8411ae359c98 -- nosy: +python-dev ___ Python tracker

[issue23581] unittest.mock.MagicMock doesn't support matmul (@) operator

Berker Peksag added the comment: Thanks for the patch, Håkan. If you want to add tests for other magic methods, please open a new issue. Thanks for the report, Zygmunt. -- resolution: -> fixed stage: commit review -> resolved status: open -> closed ___

[issue23581] unittest.mock.MagicMock doesn't support matmul (@) operator

Roundup Robot added the comment: New changeset 8c65480a1e19 by Berker Peksag in branch 'default': Issue #23581: Add matmul support to MagicMock. https://hg.python.org/cpython/rev/8c65480a1e19 -- nosy: +python-dev ___ Python tracker

[issue23651] Typo in argparse allow_abrev

New submission from Nathan West: The documentation for the new argparse feature allow_abrev contains a typo: >>> parser.add_argument('--foobar', action='store_true') >>> parser.add_argument('--foonley', action='store_false') >>> parser.parse_args([--foon]) usage: PROG [-h] [--foobar] [--foonley]

[issue23650] xml.etree.ElementTreee.write can't parse its own output

R. David Murray added the comment: Use \x escapes to construct your example, then. -- nosy: +r.david.murray ___ Python tracker ___ ___

[issue23649] tarfile not re-entrant for multi-threading

Srdjan Grubor added the comment: I don't know if that's true of core libraries. Why complicate things for end users when those issues could be done in the library itself and be completely transparent to the devs? A simple RLock latch wouldn't pose almost any speed degradation but would work in

[issue23649] tarfile not re-entrant for multi-threading

R. David Murray added the comment: If you want to use an object that has state in more than one thread you generally have to put some locking around it. Unless I'm missing something (which I might be) I don't think it is tarfile's responsibility to do this. -- nosy: +r.david.murray _

[issue23647] imaplib.py MAXLINE value is too low for gmail

Changes by R. David Murray : -- stage: -> commit review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue23647] imaplib.py MAXLINE value is too low for gmail

R. David Murray added the comment: Gmail breaks the standards again, eh? I suppose we'll have to accommodate them ;) -- components: +email nosy: +barry, r.david.murray title: imaplib.py MAXLINE value is too low for 2015 (patch attached) -> imaplib.py MAXLINE value is too low for gmail

[issue23650] xml.etree.ElementTreee.write can't parse its own output

François-Michel L'Heureux added the comment: Note that you cannot copy paste the code and expect to reproduce the issue because it contains special characters that cannot be copy pasted via a web browser. Here is the output when run. 2015-03-12 09:44:54.560 script runner plugin Hello, world

[issue23650] xml.etree.ElementTreee.write can't parse its own output

Changes by François-Michel L'Heureux : -- type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue23650] xml.etree.ElementTreee.write can't parse its own output

New submission from François-Michel L'Heureux: Using TreeBuilder to put data into XML tree. Convert that tree to a string. Parse that string. XML parser error. I expect XML library to be able to parse its own output. Reference example: https://github.com/FinchPowers/python_xml_builder_bug/blob

[issue23649] tarfile not re-entrant for multi-threading

Changes by STINNER Victor : -- nosy: +haypo, lars.gustaebel versions: +Python 3.5 ___ Python tracker ___ ___ Python-bugs-list mailing

[issue20617] test_ssl does not use mock

Roundup Robot added the comment: New changeset 2b7cf33ccd74 by Berker Peksag in branch '3.4': Issue #20617: Remove unused import in test_ssl. https://hg.python.org/cpython/rev/2b7cf33ccd74 New changeset 07e8c0ae232c by Berker Peksag in branch 'default': Issue #20617: Remove unused import in test

[issue20617] test_ssl does not use mock

Berker Peksag added the comment: Thanks Xavier and Mark. -- components: +Tests -Library (Lib) nosy: +berker.peksag resolution: -> fixed stage: -> resolved status: open -> closed versions: +Python 3.4 ___ Python tracker

[issue23649] tarfile not re-entrant for multi-threading

Srdjan Grubor added the comment: The code around tarfile multi-threading was fixed for me on the user-side with threading.Lock() usage so it might work to use this within the library and the directory creation could be improved by probably doing a try/except around the makedirs() call with ign

[issue23649] tarfile not re-entrant for multi-threading

Changes by Srdjan Grubor : -- type: enhancement -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue23649] tarfile not re-entrant for multi-threading

Srdjan Grubor added the comment: Also, extract_member in tarfile.py is not thread-safe since the check for folder existence might occur during another thread's creation of that same dir causing the code to error out. File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run

[issue23649] tarfile not re-entrant for multi-threading

Changes by Srdjan Grubor : -- type: behavior -> enhancement ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue23649] tarfile not re-entrant for multi-threading

New submission from Srdjan Grubor: When running tarfile.extract through multiple threads, the archive reading pointer is not protected from simultaneous seeks and causes various convoluted bugs: self.archive_object.extract(member, extraction_path) File "/usr/lib/python3.4/tarfile.py",

[issue23646] PEP 475: handle EINTR in the time module, retry sleep()

Charles-François Natali added the comment: As for the change to select/poll/etc, IIRC Guido was opposed to it, that's why I didn't update them. -- ___ Python tracker ___

[issue23644] g++ module compile fails with ‘_Atomic’ does not name a type

Joshua J Cogliati added the comment: If I change the header to: #ifndef Py_LIMITED_API #ifndef Py_ATOMIC_H #define Py_ATOMIC_H #include "dynamic_annotations.h" #include "pyconfig.h" #ifdef __cplusplus extern "C" { #endif #if defined(HAVE_STD_ATOMIC) #ifdef __cplusplus #include using namespac

[issue22928] HTTP header injection in urrlib2/urllib/httplib/http.client

Demian Brecht added the comment: Thanks for the tweaks Serhiy, those seem reasonable to me. -- ___ Python tracker ___ ___ Python-bugs-

[issue23644] swig compile fails with ‘_Atomic’ does not name a type

Gustavo Frederico Temple Pedrosa added the comment: @haypo, @lbianc will investigate this issue. -- ___ Python tracker ___ ___ Python-

[issue23644] swig compile fails with ‘_Atomic’ does not name a type

STINNER Victor added the comment: The problem is more general than Python: #include fails in C++. Try to compiled atomic.cpp with g++, you will get the same error. The following bug report in the glibc has been closed as WONTFIX: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60932 It suggests

[issue22038] Implement atomic operations on non-x86 platforms

Changes by Leonardo Bianconi : -- nosy: +lbianc ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue23644] swig compile fails with ‘_Atomic’ does not name a type

Changes by Leonardo Bianconi : -- nosy: +lbianc ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue23648] PEP 475 meta issue

Changes by STINNER Victor : -- nosy: +neologix ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyt

[issue23648] PEP 475 meta issue

New submission from STINNER Victor: I created this issue to group all issues related to the implementation of the PEP 475 "Retry system calls failing with EINTR". https://www.python.org/dev/peps/pep-0475/ - Issue #23646: the time module, retry sleep() - Issue #23618: the socket module - Issue #

[issue23648] PEP 475 meta issue

Changes by STINNER Victor : -- dependencies: +PEP 475 - EINTR handling, PEP 475: handle EINTR in the select and selectors module, PEP 475: handle EINTR in the socket module, PEP 475: handle EINTR in the time module, retry sleep() ___ Python tracker

[issue23646] PEP 475: handle EINTR in the time module, retry sleep()

STINNER Victor added the comment: Note: test_signal will have to be modified again when select will also retry on EINTR :-) See issue #23485. For example, test_signal.test_wakeup_fd_early() can register a signal handler which raises an exception and catch InterruptedError. --

[issue23646] PEP 475: handle EINTR in the time module, retry sleep()

STINNER Victor added the comment: Oh, test_signal fails with the patch because time.sleep() is not interrupted by a signal. New patch. I also reverted #ifdef order in floatsleep() to have a patch easier to review. -- Added file: http://bugs.python.org/file38457/sleep_eintr-2.patch ___

[issue23644] swig compile fails with ‘_Atomic’ does not name a type

Joshua J Cogliati added the comment: I have: /local/python_fix/include/python3.5m/pyatomic.h #ifndef Py_LIMITED_API #ifndef Py_ATOMIC_H #define Py_ATOMIC_H #include "dynamic_annotations.h" #include "pyconfig.h" #ifdef __cplusplus extern "C" { #endif #if defined(HAVE_STD_ATOMIC) #include #end

[issue23647] imaplib.py MAXLINE value is too low for 2015 (patch attached)

New submission from Arnt Gulbrandsen: http://stackoverflow.com/q/28923997 and various other SO questions point out that imaplib's _MAXLINE value is a bit behind the times. Fine for 1997, when people had 10MB mailbox quotas, not so fine for the age of gmail. I'm tired of seeing those questions,

[issue23646] PEP 475: handle EINTR in the time module, retry sleep()

New submission from STINNER Victor: Attached patch changes time.sleep() to retry select() when select() is interrupted by a signal or retry WaitForSingleObjectEx() when the signal SIGINT is received on Windows. The patch drops support for EMX, sorry! I didn't know EMX, I had to Google it: "EM

[issue23646] PEP 475: handle EINTR in the time module, retry sleep()

STINNER Victor added the comment: The patch includes a unit test for POSIX. For Windows, you can test manually using the attached sleep.py program: press CTRL+c to send SIGINT signals. -- Added file: http://bugs.python.org/file38455/sleep.py ___ Pyt

[issue23645] Incorrect doc for __getslice__

New submission from Gaëtan de Menten: The documentation for __getslice__ at https://docs.python.org/2/reference/datamodel.html#object.__getslice__ states: "Note that missing i or j in the slice expression are replaced by zero or sys.maxint, respectively." However, in practice, it seems like i

[issue23644] swig compile fails with ‘_Atomic’ does not name a type

Changes by STINNER Victor : -- nosy: +Vitor.de.Lima ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue22038] Implement atomic operations on non-x86 platforms

Roundup Robot added the comment: New changeset eb48295e1f8b by Victor Stinner in branch 'default': Issue #23644, #22038: Move #include inside the extern "C" { ... } https://hg.python.org/cpython/rev/eb48295e1f8b -- ___ Python tracker

[issue23644] swig compile fails with ‘_Atomic’ does not name a type

STINNER Victor added the comment: Can you please try with the latest development version? -- ___ Python tracker ___ ___ Python-bugs-li

[issue23644] swig compile fails with ‘_Atomic’ does not name a type

Roundup Robot added the comment: New changeset eb48295e1f8b by Victor Stinner in branch 'default': Issue #23644, #22038: Move #include inside the extern "C" { ... } https://hg.python.org/cpython/rev/eb48295e1f8b -- nosy: +python-dev ___ Python tracke

[issue23644] swig compile fails with ‘_Atomic’ does not name a type

STINNER Victor added the comment: _Atomic was added by the issue #22038. -- nosy: +gustavotemple, haypo ___ Python tracker ___ ___ Pyt

[issue23644] swig compile fails with ‘_Atomic’ does not name a type

New submission from Joshua J Cogliati: The attached example works fine with Python 3.4.2, but fails with Python 3.5.0a1 and 3.5.0a2 I am using: $ g++ --version g++ (GCC) 4.9.2 20150212 (Red Hat 4.9.2-6) $ swig -version SWIG Version 3.0.5 Compiled with g++ [x86_64-redhat-linux-gnu] Configured

[issue23566] RFE: faulthandler.register() should support file descriptors

STINNER Victor added the comment: Oops, I forgot Windows. On Windows, we should maybe use stderr.fileno() and avoid pass_fds. (Or maybe just skip the tests on Windows?) http://buildbot.python.org/all/builders/AMD64%20Windows7%20SP1%203.x/builds/5828/steps/test/logs/stdio =

[issue23566] RFE: faulthandler.register() should support file descriptors

STINNER Victor added the comment: > Let me know if there is possible further improvement in this patch. I was going to push your change, but I noticed that you use stderr.fileno() in tests. I modified the test to use a different file descriptor. sys.stderr is also the default value, so the tes

[issue23566] RFE: faulthandler.register() should support file descriptors

Roundup Robot added the comment: New changeset e78de5b1e3ef by Victor Stinner in branch 'default': Issue #23566: enable(), register(), dump_traceback() and dump_traceback_later() https://hg.python.org/cpython/rev/e78de5b1e3ef -- nosy: +python-dev ___

[issue23642] Interaction of ModuleSpec and C Extension Modules

David Beazley added the comment: This is great news. Read the PEP draft and think this is a very good thing to be addressing. Thanks, Brett. -- ___ Python tracker ___

[issue10967] move regrtest over to using more unittest infrastructure

Changes by Berker Peksag : -- nosy: +berker.peksag ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue23625] load_module() docs: zipped eggs are not loaded.

Brett Cannon added the comment: I understood what you asked. My point is that mentioning eggs in the imp doesn't make sense since the imp module nor import supports them natively. Eggs are a setuptools thing, not a Python standard library thing. --

[issue23642] Interaction of ModuleSpec and C Extension Modules

Brett Cannon added the comment: There is a proposed PEP on the import-sig: https://mail.python.org/pipermail/import-sig/2015-March/000904.html . I'm hoping to add it for the author to the PEP index on Friday. Basically we punted on extension modules as we ran out of time in Python 3.4. --

[issue23632] memoryview doesn't allow tuple-indexing

Stefan Krah added the comment: Yes, to be clear I'm +1 on this specific feature -- and separate issues. :) -- ___ Python tracker ___ _

[issue23632] memoryview doesn't allow tuple-indexing

Antoine Pitrou added the comment: Well, we could certainly do both :) I don't think we should weigh this issue with separate features, though. -- ___ Python tracker ___

[issue23632] memoryview doesn't allow tuple-indexing

Stefan Krah added the comment: sub-views and multi-dimensional slicing are not that bad: They're already implemented in _testbuffer (indeed with intermediate objects though). -- ___ Python tracker

[issue23632] memoryview doesn't allow tuple-indexing

Antoine Pitrou added the comment: Sub-views are not as easily implemented. Besides, they create an intermediate object which is immediately thrown away. And tuple indexing is a very common idiom in the Numpy universe. -- ___ Python tracker

[issue23632] memoryview doesn't allow tuple-indexing

Serhiy Storchaka added the comment: May be add support of multi-dimensional sub-views? >>> m = memoryview(bytearray(range(12))) >>> m2 = m.cast('B', (3,4)) >>> m2[0] Traceback (most recent call last): File "", line 1, in NotImplementedError: multi-dimensional sub-views are not implemented Th

[issue23632] memoryview doesn't allow tuple-indexing

Stefan Krah added the comment: To be sure, the PEP contains some odd proposals like "Unpacking a long-double will return a decimal object", but the one in this issue seems reasonable. -- ___ Python tracker ___

  1   2   >