[issue17594] mingw: preset configure defaults

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue27631] .exe is appended to python executable based on filesystem case insensitivity

Changes by Eryk Sun : -- stage: -> resolved ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue16353] add function to os module for getting path to default shell

Xavier de Gaye added the comment: > After several years there is still no consenus, so make it simple - the popen > and subprocess shell is one of /bin/sh, cmd.exe, or some other "hard-coded" > shell. I agree, the last patch that is being reviewed in issue 16255 attempts to do that.

[issue27632] build on AIX fails when builddir != srcdir, more than bad path to ld_so_aix

New submission from Michael Felt: Note: - Only examined on Python 2.7, but expect the same issue (from Python 3.4.X, 3.5.X and 3.6.X based on earlier attempts to use a separate builddir SUMMARY: * when builddir==srcdir build completes normally, (see DETAILS2:) * when builddir!=srcdir ... ** "co

[issue17602] mingw: default sys.path calculations for windows platforms

Martin Panter added the comment: I wonder if the PYTHONPATH preprocessor definition can just be moved from PC/pyconfig.h. It is a shame to duplicate it, and it only seems to be used in PC/getpathp.c (if you ignore Modules/getpath.c which is unused on Windows). -- components: +Windows n

[issue27633] Doc: Add missing version info to email.parser

New submission from Florian Preinstorfer: The versionchanged field has no version info for message_from_string(). -- files: email-parser-add_version_info.patch keywords: patch messages: 271442 nosy: notizblock priority: normal severity: normal status: open title: Doc: Add missing version

[issue27633] Doc: Add missing version info to email.parser

SilentGhost added the comment: LGTM -- assignee: -> docs@python components: +Documentation nosy: +SilentGhost, docs@python stage: -> commit review ___ Python tracker ___ __

[issue27633] Doc: Add missing version info to email.parser

Berker Peksag added the comment: Good catch, thanks! -- nosy: +berker.peksag resolution: -> fixed stage: commit review -> resolved status: open -> closed type: enhancement -> behavior versions: -Python 3.3, Python 3.4 ___ Python tracker

[issue27633] Doc: Add missing version info to email.parser

Roundup Robot added the comment: New changeset 3f2e37e705d3 by Berker Peksag in branch '3.5': Issue #27633: Fix usage of versionchanged directive in email.parser.rst https://hg.python.org/cpython/rev/3f2e37e705d3 New changeset 8224ad99842e by Berker Peksag in branch 'default': Issue #27633: Merg

[issue27634] selectors.SelectSelectors fails if select.select was patched

New submission from Przemyslaw Wegrzyn: The SelectSelector makes a local copy of select.select() built-in and calls it via self._select later on. It no longer works if select.select() built-in is replaced with function (something gevent's monkey patching does). Currently gevent employs a worka

[issue27634] selectors.SelectSelectors fails if select.select was patched

Przemyslaw Wegrzyn added the comment: Possible workaround in the patch attached. -- keywords: +patch Added file: http://bugs.python.org/file43910/selectors.diff ___ Python tracker __

[issue18304] ElementTree -- provide a way to ignore namespace in tags and seaches

jonathan miller added the comment: A flexible and pretty simple way opf loosening up handling namespaces would be to OPTIONALLY change what is done at parse time: 1. Don't handle xmlns declarations specially. Leave them as normal attributes, and the Element.attrib would have a normal entry f

[issue17602] mingw: default sys.path calculations for windows platforms

Steve Dower added the comment: Can MinGW build against Modules/getpath.c? I'd rather just use the posix implementation than scatter ifdefs throughout the non-posix one. -- ___ Python tracker __

[issue17599] mingw: detect REPARSE_DATA_BUFFER

Steve Dower added the comment: Worth checking if the headers in VC14 have the structure now, as it may simplify the whole thing. If not, I'd add a leading underscore to the name so nobody confuses it for public API in the future. -- ___ Python trac

[issue27630] Generator._encoded_EMTPY misspelling in email package

R. David Murray added the comment: The former is kept (IIRC) for backward compatibility, the latter should be investigated. Since I wrote that code I'll have to add this to my todo list. -- ___ Python tracker ___

[issue27634] selectors.SelectSelectors fails if select.select was patched

STINNER Victor added the comment: Monkey-patching is a bad programming practice. I don't think that Python should promote this... *But* selectors.diff LGTM. I will wait one or two weeks to let others review the patch and give their opinion. -- nosy: +haypo __

[issue23085] update internal libffi copy to 3.2.1

R. David Murray added the comment: See msg243261, I think. On linux and freebsd we could theoretically leave that to the distros, but on OSX we have to deal with it ourselves. -- nosy: +r.david.murray ___ Python tracker

[issue27626] Spelling fixes

R. David Murray added the comment: LGTM as well. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue27629] Cannot create ssl.SSLSocket without existing socket

STINNER Victor added the comment: The change introducing the != SOCK_STREAM check (change a00842b783cf) was made in 2013. It looks like the case was not tested since at least 3 years... > This will need a test in Lib/test/test_ssl.py to check for this particular > case. Yes, this new test is

[issue1521950] shlex.split() does not tokenize like the shell

Vinay Sajip added the comment: Okay, I've updated with a new patch addressing SilentGhost's comments, and addressed the comments on that patch. If I don't hear any objections by Friday, I plan to commit this change. -- ___ Python tracker

[issue1521950] shlex.split() does not tokenize like the shell

Changes by Vinay Sajip : -- assignee: -> vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue11048] "import ctypes" causes segfault on read-only filesystem

Roundup Robot added the comment: New changeset ab4975520c7d by Victor Stinner in branch '3.5': ctypes: fix CThunkObject_new() https://hg.python.org/cpython/rev/ab4975520c7d New changeset da9898e7e90d by Victor Stinner in branch 'default': Merge 3.5 (issue #11048) https://hg.python.org/cpython/re

[issue11048] "import ctypes" causes segfault on read-only filesystem

STINNER Victor added the comment: Sorry, I'm unable to reproduce the crash using the read-only filesystem. But an assertion confirmed me that the restype is not initialized which is an obvious bug. ctypes-erofs-crash.diff: LGTM. By the way, the flags field is not initialized neither, but it'

[issue11048] "import ctypes" causes segfault on read-only filesystem

Changes by Emanuel Barry : -- stage: test needed -> resolved ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue27624] unclear documentation on Queue.qsize()

STINNER Victor added the comment: """ Return the number of items in the queue. Note, in multi-threading this mostly just serves as an approximation, and information from this doesn’t guarantee that a subsequent get() or put() will not block. """ I dislike this description. If I understand corr

[issue27624] unclear documentation on Queue.qsize()

Doug Hoskisson added the comment: More explicit is ok, if that's what people want, but just not in the first sentence, because that stuff has nothing to do with what is being documented specifically (as evidenced by referencing a wikipedia article that doesn't even mention python). I don't th

[issue24214] Exception with utf-8, surrogatepass and incremental decoding

STINNER Victor added the comment: Attached patch fixes the UTF-8 decoder to support correctly incremental decoder using surrogatepass error handler. The bug occurs when b'\xed\xa4\x80' is decoded in two parts: the first two bytes (b'\xed\xa4'), and then the last byte (b'\x80'). It works as ex

[issue24214] UTF-8 incremental decoder doesn't support surrogatepass correctly

Changes by STINNER Victor : -- title: Exception with utf-8, surrogatepass and incremental decoding -> UTF-8 incremental decoder doesn't support surrogatepass correctly ___ Python tracker __

[issue27634] selectors.SelectSelectors fails if select.select was patched

Brett Cannon added the comment: I agree with Victor: monkeypatching is the wrong way to deal with this. Since SelectSelector is a class you are better off exposing something in the constructor or some method that can be overridden if this kind of flexibility is really necessary. -- no

[issue27634] selectors.SelectSelectors fails if select.select was patched

Brett Cannon added the comment: Thanks for the patch, Przemyslaw, but I'm going to close this. -- resolution: -> rejected status: open -> closed ___ Python tracker ___ _

[issue27621] incorrectly works in IDLE Query dialogs

Mark Roseman added the comment: Side note that on Mac OS X, buttons normally don't get the focus, so that this isn't an issue. Well except that buttons are getting the focus here. :-) Also since we're reinventing the wheel, please note that alternative keyboard shortcuts (e.g. command-period

[issue27635] pickle documentation says that unpickling may not call __new__

New submission from July Tikhonov: A note just below object.__setstate__() documentation https://docs.python.org/3.6/library/pickle.html#object.__setstate__ says that """ … the type should implement __getnewargs__() or __getnewargs_ex__() to establish such an invariant; otherwise, neither __new_

[issue24214] UTF-8 incremental decoder doesn't support surrogatepass correctly

Changes by Serhiy Storchaka : -- nosy: +serhiy.storchaka stage: -> patch review versions: +Python 3.5 -Python 3.4 ___ Python tracker ___

[issue18304] ElementTree -- provide a way to ignore namespace in tags and seaches

Stefan Behnel added the comment: Here is a proposed patch for a new function "strip_namespaces(tree)" that discards all namespaces from tags and attributes in a (sub-)tree, so that subsequent processing does not have to deal with them. The "__all__" test is failing (have to figure out how to f

[issue27624] unclear documentation on Queue.qsize()

R. David Murray added the comment: The current wording is, IMO, better than the suggested wording, especially if you don't want to be "teaching stuff". The current wording is a specification of the method's behavior. I really don't know what you could replace "approximate" with that would im

[issue27624] unclear documentation on Queue.qsize()

Doug Hoskisson added the comment: It is inconsistent with other documentation right next to it. Should the documentation for empty() say "Return True if the queue is approximately empty, False otherwise."? Should the documentation for full() say "Return True if the queue is approximately full,

[issue27624] unclear documentation on Queue.qsize()

Doug Hoskisson added the comment: If the specification of the empty method is to return whether the queue is empty, then the programmers have failed to meet that specification, because by the time you get that return value, it might not be empty anymore. -- ___

[issue27624] unclear documentation on Queue.qsize()

R. David Murray added the comment: The subsequent text specifies the behavior. You *could* delete the 'approximately' from the qsize documentation to be parallel, but I think that would be a disservice to the reader. You could also use the phrase "at the moment of the call" in all three, whi

[issue27624] unclear documentation on Queue.qsize()

Doug Hoskisson added the comment: My suggestion was not to delete the "approximate" entirely. Just move it out of the first sentence to make it more consistent with the other documentation. This is the model I'm seeing in empty() and full(): The first sentence is something simple and direct (w

[issue18304] ElementTree -- provide a way to ignore namespace in tags and seaches

Stefan Behnel added the comment: On second thought, I think it should be supported (also?) in the parser. Otherwise, using it with an async parser would be different from (and more involved than) one-shot parsing. That seems wrong. -- ___ Python tra

[issue27624] unclear documentation on Queue.qsize()

Changes by Raymond Hettinger : -- assignee: docs@python -> rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue24773] Implement PEP 495 (Local Time Disambiguation)

Alexander Belopolsky added the comment: It looks like Ruby folks encountered the Morocco issue [1] before us. They closed the issue on their bug tracker blaming glibc. This tells us, I guess, that we should skip this transition on the affected systems. Unfortunately, it is not just 32-bit t

[issue23085] update internal libffi copy to 3.2.1

Zachary Ware added the comment: OSX and Windows are both exempt from this discussion. Each has its own private copy of an ancient version of libffi: Modules/_ctypes/libffi_osx/ and Modules/_ctypes/libffy_msvc/. I would be in favor of switching to --with-system-ffi by default for 3.6 and depr

[issue23085] update internal libffi copy to 3.2.1

Changes by Zachary Ware : -- nosy: +ned.deily ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue18304] ElementTree -- provide a way to ignore namespace in tags and seaches

Martin Panter added the comment: Perhaps it would make more sense to use rpartition() or rstrip(). It seems possible to have a closing curly bracket in a namespace, but not in a element tag or attribute name. My guess is the __all__ failure is just a sign to add the new function to the __all_

[issue27623] int.to_bytes() and int.from_bytes(): raise ValueError when bytes count is zero

Lucas Morales added the comment: This is actually a problem in Objects/longobject.c, in the _PyLong_AsByteArray function. It should have given an overflow error, because -1 cannot be encoded in 0 bytes. -- nosy: +lucasem ___ Python tracker

[issue27623] int.to_bytes() and int.from_bytes(): raise ValueError when bytes count is zero

Changes by Anders Lorentsen : -- nosy: +Phaqui ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyt

[issue27490] Do not run pgen when it is not going to be used (cross-compiling)

Roundup Robot added the comment: New changeset c6476003e67f by Martin Panter in branch '3.5': Issue #27490: Do not build pgen when cross-compiling https://hg.python.org/cpython/rev/c6476003e67f New changeset 98df00834c58 by Martin Panter in branch 'default': Issue #27490: Merge pgen cross-compil

[issue27626] Spelling fixes

Roundup Robot added the comment: New changeset 6080d720cbf5 by Martin Panter in branch '3.5': Issue #27626: Spelling fixes in docs, comments and internal names https://hg.python.org/cpython/rev/6080d720cbf5 New changeset 3f337cce758c by Martin Panter in branch 'default': Issue #27626: Merge spel

[issue27623] int.to_bytes() and int.from_bytes(): raise ValueError when bytes count is zero

Anders Lorentsen added the comment: Isn't it possible to just add a small line of code that checks if length is less than or equal to 0, and if it is, call the necessary c functions to have python raise a valueerror...? Sorry if this is giving a solution without actually submitting the patch -

[issue27620] IDLE: Add keyboard equivalents for mouse actions.

Roundup Robot added the comment: New changeset 2468581846da by Terry Jan Reedy in branch 'default': Issue #27620: Mark the default action button as the default. https://hg.python.org/cpython/rev/2468581846da -- ___ Python tracker

[issue27621] Finish IDLE Query dialog appearance and behavior.

Terry J. Reedy added the comment: I am not trying to re-invent the wheel. I am trying to bring IDLE up to uniform standards. In particular, make all dialogs usable from the keyboard. The config dialog is the worst. See #27620, the master issue. For a two button messagebox, I went back to 3.

[issue27621] Finish IDLE Query dialog appearance and behavior.

Terry J. Reedy added the comment: I meant to direct the focus ring fix here instead #27620. To me, this issue is done, at least for now. -- ___ Python tracker ___ _

[issue27620] IDLE: Add keyboard equivalents for mouse actions.

Roundup Robot added the comment: New changeset e4a2d78aa6cc by Terry Jan Reedy in branch 'default': Issue #27620: Make htest box respond to and . https://hg.python.org/cpython/rev/e4a2d78aa6cc -- ___ Python tracker

[issue27623] int.to_bytes() and int.from_bytes(): raise ValueError when bytes count is zero

Emanuel Barry added the comment: Here's a patch that fixes this. -- components: +Interpreter Core -Library (Lib) keywords: +patch nosy: +ebarry stage: -> patch review Added file: http://bugs.python.org/file43913/int_to_bytes_overflow_1.patch ___ Pyth

[issue26942] android: test_ctypes crashes on armv7 and aarch64

Changes by Chi Hsuan Yen : -- title: android: test_ctypes crashes on armv7 -> android: test_ctypes crashes on armv7 and aarch64 ___ Python tracker ___ __

[issue27623] int.to_bytes() and int.from_bytes(): raise ValueError when bytes count is zero

Марк Коренберг added the comment: I think, we should deny: * Passing `0` to `to_bytes` (even if integer is equal to zero) * Passing empty string to `from_bytes` I do not see any use cases for this to work. It was never guaranteed to work earlier. Everyone pass constant to `to_bytes` that is >

[issue27636] Refactor IDLE htest

New submission from Terry J. Reedy: idlelib.idle_test.htest Extract a App(Tk) subclass from run function and nested function. Pass that as master instead of bare root. Extract HTest(Toplevel) class with the common code in files with an htest function. Attach HTest to App as an attribute so ht

[issue27623] int.to_bytes() and int.from_bytes(): raise ValueError when bytes count is zero

Emanuel Barry added the comment: I don't use this feature enough to have a clear opinion, however it's specifically accounted for in the code and has a test for it. It might be a good idea to bring this up on Python-ideas. It's very likely to break some code, but I wonder if said code wasn't a

[issue27637] int.to_bytes(-1, ...) should automatically choose required count of bytes

New submission from Марк Коренберг: It will be nice if `int.to_bytes` be able to automatically choose number of bytes to serialize. If so, I could write serialisation code: def serialize(value: int, signed=True) -> bytes: x = value.to_bytes(-1, 'big', signed=signed) l = value.to_bytes(4

[issue27637] int.to_bytes(-1, ...) should automatically choose required count of bytes

Марк Коренберг added the comment: Oops. def serialize(value: int, signed=True) -> bytes: x = value.to_bytes(-1, 'big', signed=signed) l = len(x).to_bytes(4, 'big', signed=False) return l + x assert len(serialize(0)) == 4 + 0 # see Issue27623 assert len(serialize(120)) == 4 + 1 asser

[issue27638] int.to_bytes() and int.from_bytes() should support 'net' and 'host' byte orders

New submission from Марк Коренберг: int.to_bytes() and int.from_bytes() should support 'net' and 'host' byte orders. I will provide a patch. -- messages: 271490 nosy: mmarkk priority: normal severity: normal status: open title: int.to_bytes() and int.from_bytes() should support 'net' an

[issue27638] int.to_bytes() and int.from_bytes() should support 'net' and 'host' byte orders

Changes by Марк Коренберг : -- components: +Library (Lib) type: -> enhancement versions: +Python 3.6 ___ Python tracker ___ ___ Pytho

[issue27638] int.to_bytes() and int.from_bytes() should support 'net' and 'host' byte orders

Emanuel Barry added the comment: Since this is a new feature addition, this should first go through Python-ideas. However, I don't think that network-related features should go into builtin types, -1 from me. -- nosy: +ebarry ___ Python tracker

[issue27490] Do not run pgen when it is not going to be used (cross-compiling)

Roundup Robot added the comment: New changeset ec27886f675f by Martin Panter in branch '2.7': Issue #27490: Do not build pgen when cross-compiling https://hg.python.org/cpython/rev/ec27886f675f -- ___ Python tracker

[issue27626] Spelling fixes

Roundup Robot added the comment: New changeset c8c1ea94379a by Martin Panter in branch '2.7': Issue #27626: Spelling fixes in docs, comments and internal names https://hg.python.org/cpython/rev/c8c1ea94379a -- ___ Python tracker

[issue23943] Misspellings in a few files

Roundup Robot added the comment: New changeset b0addbbc7671 by Martin Panter in branch '2.7': Issue #23943: Fix typos. Patch by Piotr Kasprzyk. https://hg.python.org/cpython/rev/b0addbbc7671 New changeset 48f074e2afcf by Martin Panter in branch '3.5': Issue #23943: Restore extra fixes lost in me

[issue27490] Do not run pgen when it is not going to be used (cross-compiling)

Martin Panter added the comment: FWIW I suspect this technique could be expanded to prevent Programs/_freeze_importlib from being cross-compiled, if anyone was interested. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed __

[issue18304] ElementTree -- provide a way to ignore namespace in tags and searches

Changes by Martin Panter : -- title: ElementTree -- provide a way to ignore namespace in tags and seaches -> ElementTree -- provide a way to ignore namespace in tags and searches ___ Python tracker ___

[issue27638] int.to_bytes() and int.from_bytes() should support 'net' and 'host' byte orders

Martin Panter added the comment: I wouldn’t mind the “host” byte order, assuming it just means use sys.byteorder. I think I have done this a few times, both when I really wanted the native byte order, and when I didn’t care, but assumed the native order might be slightly more efficient (e.g. b

[issue27638] int.to_bytes() and int.from_bytes() should support 'net' and 'host' byte orders

Berker Peksag added the comment: There is no need to go to python-ideas for this. Adding domain experts to nosy list is enough. -- nosy: +berker.peksag, mark.dickinson, serhiy.storchaka ___ Python tracker

[issue27637] int.to_bytes(-1, ...) should automatically choose required count of bytes

Martin Panter added the comment: I don’t like special values. A length of minus one makes no sense, so should trigger an exception, not some unexpected behaviour. A different data type like None would be a bit better. But I’m not sure this would be widely used. If you really need it you could

[issue27623] int.to_bytes() and int.from_bytes(): raise ValueError when bytes count is zero

Martin Panter added the comment: I agree that the signed conversion cases should be an error. However the unsigned case would break working code that I have written for bijective numeration. See _bytes_to_int() and _int_to_bytes() in Issue 20132, inc-codecs.diff, for example. Since non-zero un

[issue27626] Spelling fixes

Martin Panter added the comment: Thanks for the patch -- resolution: -> fixed stage: commit review -> resolved status: open -> closed versions: +Python 2.7 ___ Python tracker __

[issue17605] mingw-meta: build interpeter core

Changes by Martin Panter : -- dependencies: +mingw: use main() to start execution ___ Python tracker ___ ___ Python-bugs-list mailing

[issue27638] int.to_bytes() and int.from_bytes() should support 'net' and 'host' byte orders

Serhiy Storchaka added the comment: I agreed with Martin. The "host" byte order is sys.byteorder, and the "net" byteorder is just "big". There is one obvious way to specify this, and there is not need to add yet one way. Adding support of new values for byteorder would complicate and slow down

[issue27637] int.to_bytes(-1, ...) should automatically choose required count of bytes

Serhiy Storchaka added the comment: This is rarely needed, mainly in general serializers like pickle. The code for determining the minimal number of bytes is not trivial, but it depends on the serializer. If you always serialize unsigned values and saves the sign separately, or use one's compl

[issue27639] UserList.__getitem__ doesn't account for slices

New submission from Anton Backer: The docs for UserList say: > List operations which return a new sequence attempt to create an instance of > the actual implementation class. However, UserList([])[:] returns a list, not a UserList. -- components: Library (Lib) files: patch messages: 2

[issue27623] int.to_bytes() and int.from_bytes(): raise ValueError when bytes count is zero

Serhiy Storchaka added the comment: I agree with Martin. The ambiguous signed conversion cases should be an error, the unambiguous unsigned conversion case should be supported (especially if there are tests for this). -- nosy: +serhiy.storchaka ___

[issue27639] UserList.__getitem__ doesn't account for slices

Changes by Serhiy Storchaka : -- assignee: -> rhettinger nosy: +rhettinger, serhiy.storchaka priority: normal -> low ___ Python tracker ___ _

[issue27639] UserList.__getitem__ doesn't account for slices

Changes by Anton Backer : -- hgrepos: +351 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.

[issue27590] tarfile module next() method hides exceptions

Lars Gustäbel added the comment: After all these years, it is not that easy to say why the decision to swallow this exception was made. One part surely was a lack of experience with the tar format itself and all of its implementations. The other part I guess was that it was supposed to avoid p