[issue29757] The loop in utility `socket.create_connection()` swallows previous errors

Yury Selivanov added the comment: This is a new feature, so we can only push it to 3.7. -- nosy: +brett.cannon, haypo versions: -Python 2.7, Python 3.3, Python 3.4, Python 3.5, Python 3.6 ___ Python tracker

[issue29758] Previously-working SWIG code fails in Python 3.6

Tristan Croll added the comment: Nope - belay that. Checking through the SWIG-generated Python code, all the classes correctly inherit from object, which negates that issue. -- ___ Python tracker

[issue29772] Unintentionally deleted line on library/collections.rst

Raymond Hettinger added the comment: Nice catch. -- nosy: +rhettinger resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker

[issue29774] Improve zipfile handling of corrupted extra field

STINNER Victor added the comment: I merged your PR, thanks! I don't think that this minor enhancement on error message is worth it to be backported. It only impacts corrupted ZIP files, and 3.6 and older already raise an error message. I updated manually the PR status, it seems like the

[issue29776] Modernize properties

Serhiy Storchaka added the comment: I replaced only private getters and setters. All tests passed. -- ___ Python tracker ___

[issue29774] Improve zipfile handling of corrupted extra field

Changes by Serhiy Storchaka : -- pull_requests: +480 ___ Python tracker ___ ___

[issue29752] Enum._missing_ not called for __getattr__ failures

Ethan Furman added the comment: Thank you, Josh, that's a very good point. One can be expected to have the correct spelling when using attribute access. So the two accesses that make sense for a _missing_ call would then be: - by-value lookup (e.g. Label(1)) - by-name lookup (e.g.

[issue29774] Improve zipfile handling of corrupted extra field

Changes by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue29757] The loop in utility `socket.create_connection()` swallows previous errors

Yury Selivanov added the comment: > Case (c) sidesteps the above questions. I like the (c) option. I don't think we should use logging/warnings here, as they can produce unwanted noise that few know how to silence. When the list of errors is passed as a second argument to the exception, how

[issue29775] There appears to be a spurious ^0 in sys.version for 3.6.1rc1

New submission from Paul Moore: The 3.6.1rc1 build seems to have a spurious "^0" at the end of the version, before the VCS ID - 3.6.1rc1^0): >py -3.6 Python 3.6.1rc1 (v3.6.1rc1^0:e0fbe5feee4f9c00f09eb9659c2182183036261a, Mar 4 2017, 20:00:12) [MSC v.1900 64 bit (AMD64)] on win32 >>>

[issue29674] Use GCC __attribute__((alloc_size(x, y))) on PyMem_Malloc() functions

STINNER Victor added the comment: > So once these functions are decorated with this attribute, what kind of > testing/validation you have in mind, please let me know. Call PyMem_Malloc(Py_ssize_t) for example: it must emit a warning on GCC 7, since casting negative values to size_t overflows.

[issue29772] Unintentionally deleted line on library/collections.rst

Changes by Serhiy Storchaka : -- nosy: +serhiy.storchaka ___ Python tracker ___

[issue29776] Modernize properties

New submission from Serhiy Storchaka: Following PR updates Python sources to use new shiny syntax for properties. It replaces the old code def _foo(self): ... def _set_foo(self, value): ... foo = property(_foo, _set_foo) with the new code @property def

[issue29776] Modernize properties

Ethan Furman added the comment: Have you made sure nothing calls the replaced functions manually? Such as: ... self._set_foo(9) ... -- nosy: +ethan.furman ___ Python tracker

[issue29674] Use GCC __attribute__((alloc_size(x, y))) on PyMem_Malloc() functions

svelankar added the comment: So once these functions are decorated with this attribute, what kind of testing/validation you have in mind, please let me know. -- nosy: +svelankar ___ Python tracker

[issue29774] Improve zipfile handling of corrupted extra field

New submission from Serhiy Storchaka: The zipfile module can raise struct.error when process corrupted extra field. This issue was partially resolved by issue14315. Following PR converts struct.error to BadZipFile in other case. -- components: Library (Lib) messages: 289302 nosy:

[issue29774] Improve zipfile handling of corrupted extra field

Changes by Serhiy Storchaka : -- type: behavior -> enhancement versions: -Python 2.7, Python 3.5, Python 3.6 ___ Python tracker

[issue29319] Embedded 3.6.0 distribution cannot run pyz files

Paul Moore added the comment: Confirmed that 3.6.1rc1 fixes the issue in my original use case. -- ___ Python tracker ___

[issue29776] Modernize properties

Changes by Serhiy Storchaka : -- pull_requests: +482 ___ Python tracker ___ ___

[issue29774] Improve zipfile handling of corrupted extra field

Serhiy Storchaka added the comment: I think the same. -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue29772] Unintentionally deleted line on library/collections.rst

Changes by Roundup Robot : -- pull_requests: +478 ___ Python tracker ___

[issue28685] Optimizing list.sort() by performing safety checks in advance

Changes by Elliot Gorokhovsky : -- pull_requests: +479 ___ Python tracker ___

[issue29619] st_ino (unsigned long long) is casted to long long in posixmodule.c:_pystat_fromstructstat

Changes by STINNER Victor : -- pull_requests: +481 ___ Python tracker ___ ___

[issue29758] Previously-working SWIG code fails in Python 3.6

Tristan Croll added the comment: OK, this seems to narrow down the problem. The following was legal in Python 3.5.1, but in 3.5.3 and 3.6.1rc1 returns: 'TypeError: must be type, not classobj' class Foo_Base: pass class Bar_Base: def get_foo(self): f = Foo_Base()

[issue29770] Executable help output (--help) at commandline is wrong for option -B

Changes by Xiang Zhang : -- pull_requests: +486 ___ Python tracker ___ ___ Python-bugs-list

[issue29778] _Py_CheckPython3 uses uninitialized dllpath when embedder sets module path with Py_SetPath

New submission from Tibor Csonka: When Py_SetPath is used to set up module path at initialization, the Py_SetPath causes getpathp.c::calculate_path not to be called. However, calculate path is the only function calling getpathp.c::get_progpath which initializes the local dllpath static

[issue29772] Unintentionally deleted line on library/collections.rst

New submission from Kinebuchi Tomohiko: The last part of "Counter objects" section has a strange line: "in Smalltalk." https://docs.python.org/2.7/library/collections.html#counter-objects The line just before "in Smalltalk" might be deleted by accident. Related issue is bpo-25910 [1]_ and the

[issue29773] Additional float-from-string tests

New submission from Serhiy Storchaka: Following PR adds more corner cases in the test for calling float() with invalid string. -- components: Tests messages: 289301 nosy: serhiy.storchaka priority: normal severity: normal stage: patch review status: open title: Additional

[issue29758] Previously-working SWIG code fails in Python 3.6

Tristan Croll added the comment: Sorry - ignore that. Brain-fart at the end of a (very) long day. -- versions: -Python 3.5 ___ Python tracker ___

[issue29758] Previously-working SWIG code fails in Python 3.6

Brett Cannon added the comment: Since it sounds like everything on the Python side is fine I'm closing this. -- nosy: +brett.cannon resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker

[issue29769] pkgutil._iter_file_finder_modules should not be fooled by *.py folders

Changes by Brett Cannon : -- nosy: -brett.cannon ___ Python tracker ___ ___

[issue26744] print() function hangs on MS-Windows 10

Eryk Sun added the comment: > After enabling `QuickEdit Mode`, then click the console will > suspend the program. That's not suspending the entire process. It's blocking the thread that writes to the console. The user-mode WriteConsole function is implemented by a synchronous

[issue29758] Previously-working SWIG code fails in Python 3.6

STINNER Victor added the comment: The code in msg289314 doesn't emit any warning. I tested 3.5, 3.6 and master development branches and system Python 3.5.2. -- ___ Python tracker

[issue28298] can't set big int-like objects to items in array 'Q', 'L' and 'I'

Changes by Oren Milman : -- pull_requests: +485 ___ Python tracker ___ ___ Python-bugs-list

[issue29773] Additional float-from-string tests

Changes by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue29758] Previously-working SWIG code fails in Python 3.6

Tristan Croll added the comment: I've cross-posted the following to the SWIG bug tracker. Hopefully someone can find an answer, because I'm getting nowhere. If I have two classes Foo and Bar (where Bar has a function get_foo() that returns a Foo object) defined in the SWIG-generated library

[issue29758] Previously-working SWIG code fails in Python 3.6

STINNER Victor added the comment: "Nope - belay that. Checking through the SWIG-generated Python code, all the classes correctly inherit from object, which negates that issue." I don't understand your comment, on Python 3, any class inherit from object be default. There is no more old and new

[issue29773] Additional float-from-string tests

Changes by Serhiy Storchaka : -- pull_requests: +483 ___ Python tracker ___ ___

[issue29773] Additional float-from-string tests

Changes by Serhiy Storchaka : -- pull_requests: +484 ___ Python tracker ___ ___

[issue29758] Previously-working SWIG code fails in Python 3.6

Tristan Croll added the comment: I don't agree that it should be closed yet. I still have the issue that an approach that was perfectly legal in Python 3.5 now no longer works in Python 3.6, and I don't know why. The description in msg289281 stands, and is a real problem. Nothing has changed

[issue29751] PyLong_FromString documentation wrong on numbers with leading zero and base=0

Changes by Brett Cannon : -- title: PyLong_FromString fails on decimals with leading zero and base=0 -> PyLong_FromString documentation wrong on numbers with leading zero and base=0 ___ Python tracker

[issue29777] argparse arguments in main parser hide an argument in subparser

Eric V. Smith added the comment: No, we won't be adding new features to 2.7. Sorry. -- nosy: +eric.smith resolution: -> rejected stage: -> resolved type: -> enhancement ___ Python tracker

[issue29776] Modernize properties

Serhiy Storchaka added the comment: I have checked and none from replaced function is used. But just for the case I reverted changes for Lib/xml/dom/. Here used more complex logic for generating other properties. -- ___ Python tracker

[issue29765] 2.7.12 compile error from ssl related

Christian Heimes added the comment: /usr/local looks wrong. Did you install a custom build of OpenSSL? What's the output of rpm -qf /usr/local/include/openssl/asn1.h ? -- ___ Python tracker

[issue19974] tarfile doesn't overwrite symlink by directory

Changes by Serhiy Storchaka : -- nosy: +haypo ___ Python tracker ___ ___

[issue27850] Remove 3DES from cipher list (sweet32 CVE-2016-2183)

Changes by STINNER Victor : -- priority: critical -> release blocker ___ Python tracker ___

[issue27850] Remove 3DES from cipher list (sweet32 CVE-2016-2183)

Larry Hastings added the comment: I've accepted PR 224. I don't plan an emergency release of 3.4 to get this change out into the world. Unless there's any other business, we can now close this issue. -- resolution: -> fixed stage: commit review -> resolved status: open -> closed

[issue29752] Enum._missing_ not called for __getattr__ failures

Josh Rosenberg added the comment: Yeah, that sounds fine. -- ___ Python tracker ___ ___ Python-bugs-list

[issue29775] There appears to be a spurious ^0 in sys.version for 3.6.1rc1

Ned Deily added the comment: Thanks, Paul, we are aware of the spurious ^0. It will be resolved under Issue 25793. -- priority: release blocker -> resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Deprecate sys._mercurial and create sys._git

[issue29777] argparse arguments in main parser hide an argument in subparser

New submission from Alan Evangelista: If you have a argument named -- in a subparser and two arguments named -- in the main parser and call the Python executable with python -- argparse fails with: error: ambiguous option: -- could match --, -- This probably happens due to

[issue28739] PEP 498: docstrings as f-strings

Changes by Mariatta Wijaya : -- pull_requests: +487 ___ Python tracker ___ ___

[issue28739] PEP 498: docstrings as f-strings

Changes by Mariatta Wijaya : -- stage: needs patch -> patch review ___ Python tracker ___

[issue28739] PEP 498: docstrings as f-strings

Mariatta Wijaya added the comment: Hi, I updated the documentation mentioning that f-strings cannot be used as docstring. Please review it. Thanks. -- nosy: +Mariatta ___ Python tracker

[issue29258] __init__.py required for pkgutil.walk_packages in python3

Changes by Wolfgang Maier : -- nosy: +wolma ___ Python tracker ___

[issue17062] An os.walk inspired replacement for pkgutil.walk_packages

Changes by Wolfgang Maier : -- nosy: +wolma ___ Python tracker ___

[issue19821] pydoc.ispackage() could be more accurate

Changes by Wolfgang Maier : -- nosy: +wolma ___ Python tracker ___

[issue28685] Optimizing list.sort() by performing safety checks in advance

Serhiy Storchaka added the comment: The issue shouldn't be closed until it resolved or rejected. I like the idea, and benchmarking results for randomized lists look nice. But could you please run benchmarks for already sorted lists? -- nosy: +serhiy.storchaka stage: resolved -> patch

[issue20087] Mismatch between glibc and X11 locale.alias

Benjamin Peterson added the comment: Do you believe this program should work? import locale, os for l in open("/usr/share/i18n/SUPPORTED"): alias, encoding = l.strip().split() locale.setlocale(locale.LC_ALL, alias) try: enc = locale.getlocale()[1] except ValueError:

[issue29779] New environment variable PYTHONHISTORY

Changes by Levi Sabah <0xl...@gmail.com>: -- nosy: 0xl3vi priority: normal pull_requests: 488 severity: normal status: open title: New environment variable PYTHONHISTORY versions: Python 3.7 ___ Python tracker

[issue29319] Embedded 3.6.0 distribution cannot run pyz files

Nick Coghlan added the comment: Issue 29723 is a follow up issue to this one, where these changes revealed some latent defects in how sys.path[0] was being initialised in general for directory and zipfile execution (those defects mean the change committed here adds an extra directory to

[issue29769] pkgutil._iter_file_finder_modules should not be fooled by *.py folders

Nick Coghlan added the comment: I think there's an open issue somewhere pointing out that _iter_file_finder doesn't handle PEP 420 namespace packages correctly, precisely because it's still looking for an __init__.py file. So I'd suggest not worry about changing the __init__.py handling here,

[issue29773] Additional float-from-string tests

Changes by Serhiy Storchaka : -- pull_requests: +477 ___ Python tracker ___ ___

[issue29679] Add @contextlib.asynccontextmanager

Nick Coghlan added the comment: For anyone interested in the question of backports, I moved that discussion over to the contextlib2 tracker: https://github.com/jazzband/contextlib2/issues/12 -- ___ Python tracker

[issue28298] can't set big int-like objects to items in array 'Q', 'L' and 'I'

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

[issue15988] Inconsistency in overflow error messages of integer argument

Serhiy Storchaka added the comment: The patch no longer applied cleanly (in particular to arraymodule.c). Oren, could you please update it? -- ___ Python tracker

[issue29768] Fix expact version check

Changes by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue29758] Previously-working SWIG code fails in Python 3.6

STINNER Victor added the comment: Which function raises this exception? Add the traceback place. It may be a bug in your code. -- ___ Python tracker ___

[issue20087] Mismatch between glibc and X11 locale.alias

Serhiy Storchaka added the comment: The SUPPORTED file from glibc is used for determining the default encoding for locales that don't include it explicitly. For example en_IN uses UTF-8 rather than ISO8859-1. -- ___ Python tracker

[issue20087] Mismatch between glibc and X11 locale.alias

Marc-Andre Lemburg added the comment: On 09.03.2017 08:15, Benjamin Peterson wrote: > > "eo_XX" is just something that appears in the X11 locale.alias file. My > change doesn't add that; it was already there. (for Esperanto, which I > suppose explains the "XX") Yes, I know. That was an

[issue29758] Previously-working SWIG code fails in Python 3.6

Tristan Croll added the comment: OK, a further clue. First, a little more detail on how my project is arranged (to re-iterate, this works without complaint in Python 3.5): Rather than use my SWIG output directly, I've created a further wrapper layer in Python to add functions/syntactic sugar

[issue20087] Mismatch between glibc and X11 locale.alias

Serhiy Storchaka added the comment: > Why is the X11 locale alias map used at all? It seems like it can only create > confusion with libc. Originally only the X11 locale alias map was used. The support of the glibc locale alias map was added 2.5 years ago (issue20079). --

[issue29768] Fix expact version check

Changes by Serhiy Storchaka : -- pull_requests: +474 ___ Python tracker ___ ___

[issue29768] Fix expact version check

Changes by Serhiy Storchaka : -- pull_requests: +473 ___ Python tracker ___ ___

[issue29768] Fix expact version check

Changes by Serhiy Storchaka : -- pull_requests: +475 ___ Python tracker ___ ___

[issue20087] Mismatch between glibc and X11 locale.alias

Marc-Andre Lemburg added the comment: On 09.03.2017 11:47, Serhiy Storchaka wrote: > > The SUPPORTED file from glibc is used for determining the default encoding > for locales that don't include it explicitly. For example en_IN uses UTF-8 > rather than ISO8859-1. No, the glibc locales don't

[issue26744] print() function hangs on MS-Windows 10

Ma Lin added the comment: This is an invalid issue, very sorry for waste your time! Especially apologize to Stinner. After enabling `QuickEdit Mode`, then click the console will suspend the program. -- resolution: -> not a bug stage: -> resolved status: open -> closed

[issue20087] Mismatch between glibc and X11 locale.alias

Serhiy Storchaka added the comment: The original issue is issue29571. The locale module returned encoding ISO8859-1 for locale en_IN (as in the X11 locale alias map), but glibc uses UTF-8 (as in glibc SUPPORT file). -- ___ Python tracker

[issue29770] Executable help output (--help) at commandline is wrong for option -B

New submission from Wolfgang Langner: The output for "python --help" for the option -B is wrong. It contains also the old pyo files. But they were removed. Output is: -B : don't write .py[co] files on import; also PYTHONDONTWRITEBYTECODE=x should be: -B : don't write .pyc files on

[issue29619] st_ino (unsigned long long) is casted to long long in posixmodule.c:_pystat_fromstructstat

Mba added the comment: > I don't think that a filesystem produce inodes larger than 2^63-1 The problem is real: the large inode number was assigned to a file created by MacOS on a share exported via CIFS, and then stated by Linux using NFS export. --

[issue29771] An email and MIME handling package - Add support to send CC of email

New submission from Jack: Currently using the package we can only define emails in the 'TO' as shown here: https://docs.python.org/2/library/email-examples.html#email-examples There is no support for email to be sent as CC or BCC which is useful quality in many emails. Please see if this can

[issue29769] pkgutil._iter_file_finder_modules should not be fooled by *.py folders

New submission from Wolfgang Maier: The current implementation of _iter_file_finder_modules parses folders with a valid Python module extension as modules (e.g. it would report a *folder* xy.py as a module xy). As a result, e.g., pydoc.apropos('') fails if such a folder is found anywhere on

[issue29771] An email and MIME handling package - Add support to send CC of email

Eric V. Smith added the comment: The examples don't cover it, but look at the documentation for setting arbitrary mail headers such as CC. And look at smtplib.SMTP.sendmail() on sending a message to arbitrary recipients (to, cc, or bcc are all the same):

[issue29771] An email and MIME handling package - Add support to send CC of email

Jack added the comment: Please see the stack overflow question: http://stackoverflow.com/questions/42696100/python-smtp-send-email-with-cc -- ___ Python tracker

[issue29771] An email and MIME handling package - Add support to send CC of email

Eric V. Smith added the comment: You need to review how SMTP works. The contents of the mail message have no bearing on where messages are sent. That's exactly how BCC works: there's nothing in the message telling you who is BCC'd, but the mail is still sent to the BCC recipients, via SMTP.

[issue29769] pkgutil._iter_file_finder_modules should not be fooled by *.py folders

Changes by Serhiy Storchaka : -- nosy: +brett.cannon, eric.snow ___ Python tracker ___

[issue29770] Executable help output (--help) at commandline is wrong for option -B

Changes by Serhiy Storchaka : -- nosy: +brett.cannon ___ Python tracker ___ ___

[issue28298] can't set big int-like objects to items in array 'Q', 'L' and 'I'

Changes by Oren Milman : -- pull_requests: +476 ___ Python tracker ___ ___ Python-bugs-list

[issue29771] An email and MIME handling package - Add support to send CC of email

Jack added the comment: But this is what I mean.. It shouldn't be arbitrary. When you define CC you want him as CC not as another one in the TO. This is why I said this is enhancement request. -- ___ Python tracker

[issue29771] An email and MIME handling package - Add support to send CC of email

Changes by Jack : -- status: closed -> open ___ Python tracker ___ ___ Python-bugs-list

[issue29771] An email and MIME handling package - Add support to send CC of email

Eric V. Smith added the comment: So, you want to improve the examples? I wouldn't be opposed to that. I don't see that there's any code to change. -- assignee: -> docs@python components: +Documentation nosy: +docs@python ___ Python tracker

[issue29771] An email and MIME handling package - Add support to send CC of email

Jack added the comment: I think you missundersttod. I showed the example page just so you would understand what I am talking about. Let me explain it better: msg['Subject'] = 'The contents of %s' % textfile msg['From'] = me msg['To'] = you Works. msg['Subject'] = 'The contents of %s' %

[issue29771] An email and MIME handling package - Add support to send CC of email

R. David Murray added the comment: If you use smtplib.send_message in python3, it will do what you want (including stripping BCC headers before sending the message). If someone wants to create a PR to add an example of what Eric is talking about (specifying additional senders in

[issue29771] An email and MIME handling package - Add support to send CC of email

Changes by Serhiy Storchaka : -- components: +email nosy: +barry, r.david.murray ___ Python tracker ___

[issue29771] An email and MIME handling package - Add support to send CC of email

Jack added the comment: "I'm on the fence about including this in the examples." Think of it this way.. Including it in the docs would have prevented this question. It can be just a side note it doesn't have to be a whole example. Thx. -- status: open -> closed