[issue22493] Deprecate the use of flags not at the start of regular expression

Matthew Barnett added the comment: I downloaded Python 3.6.0b1 not long after it was released and it works for me: >>> re.match('(?i:CaseInsensitive)', 'caseinsensitive') <_sre.SRE_Match object; span=(0, 15), match='caseinsensitive'> -- ___ Python tr

[issue28145] Fix whitespace in C source code

Roundup Robot added the comment: New changeset 2a97b5ab6132 by Martin Panter in branch '2.7': Issue #28145: Spelling fixes https://hg.python.org/cpython/rev/2a97b5ab6132 New changeset 02dd99aeba7d by Martin Panter in branch '3.5': Issue #28145: Spelling fixes https://hg.python.org/cpython/rev/02

[issue24366] Simple indentation

Roundup Robot added the comment: New changeset 8aa93fd7db2d by Martin Panter in branch '2.7': Issue #24366: Fix indentation https://hg.python.org/cpython/rev/8aa93fd7db2d -- ___ Python tracker _

[issue28143] ASDL compatibility with Python 3 system interpreter

Martin Panter added the comment: It seems a terrible idea to require Python 3 to be installed in order to regenerate the boot files for a Python 2 build. Maybe if we can figure out the minimum installed Python version expected for these ASDL scripts in 2.7, and maintain that while adding Pytho

[issue28143] ASDL compatibility with Python 3 system interpreter

R. David Murray added the comment: Yes, by "fix this" I meant make it work under both python2 and python3. But failing that, the status quo wins. -- ___ Python tracker ___

[issue28139] Misleading Indentation in C source code

Martin Panter added the comment: . I found more messed up indentation looking through Antoine’s large “untabify” commit r81029. These don’t trigger compiler warnings, but I think it may be worth restoring them. -- nosy: +martin.panter stage: resolved -> patch review status: closed -> o

[issue28128] Improve the warning message for invalid escape sequences

Nick Coghlan added the comment: Adding a "DeprecatedSyntaxWarning" that's a subclass of both DeprecationWarning and SyntaxWarning (and hence silenced by default while still having the extra SyntaxWarning attributes) strikes me as a reasonable step to take here, even though we're into the beta

[issue28143] ASDL compatibility with Python 3 system interpreter

Martin Panter added the comment: Another option I forgot to point out is that some of the other regeneration Python scripts (in Py 2 and/or 3; I forget which) have some autoconf magic to figure out the right installed python command to use. We should probably use that for Py 2’s ASDL script.

[issue28139] Misleading Indentation in C source code

Changes by Martin Panter : Added file: http://bugs.python.org/file44683/indent.patch ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue28139] Misleading Indentation in C source code

Changes by Martin Panter : Added file: http://bugs.python.org/file44684/indent.py3.patch ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue28134] socket.socket(fileno=fd) does not work as documented

Martin Panter added the comment: I agree the doc is far from perfect. The bit I was going off is just above , saying “these (read-only) attributes that correspond to the values given to the socket constructor”. My instinct

[issue28128] Improve the warning message for invalid escape sequences

Emanuel Barry added the comment: Thank you Nick for the useful feedback! I think that a subclass of DeprecationWarning and SyntaxWarning would be a good idea; I'll play around with that. As far as when the warning should occur, I agree that erroring out at the compile step isn't optimal, howe

[issue28128] Improve the warning message for invalid escape sequences

Yury Selivanov added the comment: BTW, this will also help to make warnings more friendly in #26182. -- ___ Python tracker ___ ___ Pyt

[issue28128] Improve the warning message for invalid escape sequences

Nick Coghlan added the comment: I realised I wasn't entirely clear about the "warning misattribution" problem that's implied by Chi Hsuan's problem report, so here's the behaviour when using "-W all" rather than "-W error": $ echo "print('\d')" > bad_escape.py $ echo "import bad_escape

[issue27348] traceback (and threading) drops exception message

Martin Panter added the comment: I plan to commit this soon, in time for the next release. -- stage: patch review -> commit review versions: +Python 3.7 ___ Python tracker ___ __

[issue28128] Improve the warning message for invalid escape sequences

Nick Coghlan added the comment: Regarding when I think the error should be generated, we definitely want the warning to be happening at compile time, but the "compile step" is actually a series of substeps. The point where the string parser is processing string escapes is *not* the best place

[issue28128] Improve the warning message for invalid escape sequences

Emanuel Barry added the comment: Hmm, I see; I'll need to dig a bit deeper get to and understand that part of the compile process better. I'll look up where SyntaxErrors are generated (since they have access to at least the line number at that point), and try to hook it up from there. ---

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Martin Panter added the comment: Just to clarify, the current status is that the revision that Koobs identified is still in place, meaning that the AST files are regenerated into the build tree, not the source tree. I don’t think there is much else to do for this bug, unless Koobs can provide

[issue28128] Improve the warning message for invalid escape sequences

Nick Coghlan added the comment: I've added Eric Smith to the nosy list as well, as he's been working on that part of the compilation pipeline for the f-string implementation. Eric, the context here is that the new deprecation warning for unknown escapes is currently being misattributed to the

[issue27374] Cygwin: Makefile does not install DLL import library

Masayuki Yamamoto added the comment: I found -L option addition at Lib/distutils/command/build_ext.py:222. This place is a process that finalize options for the build_ext command. Comment in there: for extensions under Cygwin and AtheOS Python's library directory must be appended to library_di

[issue24363] httplib fails to handle semivalid HTTP headers

Roundup Robot added the comment: New changeset c38e10ad7c89 by Martin Panter in branch '2.7': Issue #24363: Continue parsing HTTP header in spite of invalid lines https://hg.python.org/cpython/rev/c38e10ad7c89 -- nosy: +python-dev ___ Python tracker

[issue10765] Build regression from automation changes on windows

Zachary Ware added the comment: The build system has been completely rewritten at least once since this was opened; this should no longer be a problem. -- resolution: -> out of date stage: patch review -> resolved status: open -> closed ___ Python t

[issue24363] httplib fails to handle semivalid HTTP headers

Martin Panter added the comment: I pushed my Py 2 patch, since it is simpler and does not interfere with other modules. But it would still be good to get feedback on policy-flag.patch for Python 3. -- ___ Python tracker

[issue26149] Suggest PyCharm Community as an editor for Unix platforms

Mariatta Wijaya added the comment: Mention Pycharm community edition, and provide link to the wiki -- keywords: +patch nosy: +Mariatta Wijaya Added file: http://bugs.python.org/file44686/docupdate.patch ___ Python tracker

[issue28176] Fix callbacks race in asyncio.SelectorLoop.sock_connect

Changes by Berker Peksag : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue28177] Compilation failure on Debian 4

New submission from David: Hi there. On Debian 4, while running 'make' against a downloaded and extracted Python-3.6.0b1.tar.xz, I get this error: gcc -pthread -c -fno-strict-aliasing -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes-std=c99 -Wextra -Wn

[issue28177] Compilation failure on Debian 4

Benjamin Peterson added the comment: We don't support GCC versions < 4.3 anymore. -- nosy: +benjamin.peterson resolution: -> wont fix status: open -> closed ___ Python tracker _

[issue28177] Compilation failure on Debian 4

David added the comment: Thanks. What is the last official version of Python which does support GCC versions < 4.3 ? On Fri, Sep 16, 2016 at 7:20 AM, Benjamin Peterson wrote: > > Benjamin Peterson added the comment: > > We don't support GCC versions < 4.3 anymore. > > -- > nosy: +benj

[issue28177] Compilation failure on Debian 4

Benjamin Peterson added the comment: 3.5 probably works. On Thu, Sep 15, 2016, at 22:21, David wrote: > > David added the comment: > > Thanks. > > What is the last official version of Python which does support GCC > versions > < 4.3 ? > > On Fri, Sep 16, 2016 at 7:20 AM, Benjamin Peterson >

[issue28177] Compilation failure on Debian 4

Changes by Zachary Ware : -- stage: -> resolved ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue28177] Compilation failure on Debian 4

Martin Panter added the comment: For the record, there is more discussion of this in Issue 28092 -- nosy: +martin.panter superseder: -> Build failure for 3.6 on Centos 5.11 ___ Python tracker _

<    1   2   3