[issue28177] Compilation failure on Debian 4

[Martin Panter]

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28177] Compilation failure on Debian 4

[Zachary Ware]

Changes by Zachary Ware :


--
stage:  -> resolved

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28177] Compilation failure on Debian 4

[Benjamin Peterson]

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
> 
> wrote:
> 
> >
> > 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 
> > 
> > ___
> >
> 
> --
> 
> ___
> Python tracker 
> 
> ___

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28177] Compilation failure on Debian 4

[David]

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: +benjamin.peterson
> resolution:  -> wont fix
> status: open -> closed
>
> ___
> Python tracker 
> 
> ___
>

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28177] Compilation failure on Debian 4

[Benjamin Peterson]

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28177] Compilation failure on Debian 4

[David]

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 -Wno-unused-parameter 
-Wno-missing-field-initializers   -I. -IInclude -I./Include-DPy_BUILD_CORE \
  -DHGVERSION="\"`LC_ALL=C `\"" \
  -DHGTAG="\"`LC_ALL=C `\"" \
  -DHGBRANCH="\"`LC_ALL=C `\"" \
  -o Modules/getbuildinfo.o ./Modules/getbuildinfo.c
gcc -pthread -c -fno-strict-aliasing -Wsign-compare -DNDEBUG -g -fwrapv -O3 
-Wall -Wstrict-prototypes-std=c99 -Wextra -Wno-unused-parameter 
-Wno-missing-field-initializers   -I. -IInclude -I./Include-DPy_BUILD_CORE 
-o Programs/_freeze_importlib.o Programs/_freeze_importlib.c
gcc -pthread   -o Programs/_freeze_importlib Programs/_freeze_importlib.o 
Modules/getbuildinfo.o Parser/acceler.o Parser/grammar1.o Parser/listnode.o 
Parser/node.o Parser/parser.o Parser/bitset.o Parser/metagrammar.o 
Parser/firstsets.o Parser/grammar.o Parser/pgen.o Parser/myreadline.o 
Parser/parsetok.o Parser/tokenizer.o Objects/abstract.o Objects/accu.o 
Objects/boolobject.o Objects/bytes_methods.o Objects/bytearrayobject.o 
Objects/bytesobject.o Objects/cellobject.o Objects/classobject.o 
Objects/codeobject.o Objects/complexobject.o Objects/descrobject.o 
Objects/enumobject.o Objects/exceptions.o Objects/genobject.o 
Objects/fileobject.o Objects/floatobject.o Objects/frameobject.o 
Objects/funcobject.o Objects/iterobject.o Objects/listobject.o 
Objects/longobject.o Objects/dictobject.o Objects/odictobject.o 
Objects/memoryobject.o Objects/methodobject.o Objects/moduleobject.o 
Objects/namespaceobject.o Objects/object.o Objects/obmalloc.o Objects/capsule.o 
Objects/rangeobject.o Objects/seto
 bject.o Objects/sliceobject.o Objects/structseq.o Objects/tupleobject.o 
Objects/typeobject.o Objects/unicodeobject.o Objects/unicodectype.o 
Objects/weakrefobject.o Python/_warnings.o Python/Python-ast.o Python/asdl.o 
Python/ast.o Python/bltinmodule.o Python/ceval.o Python/compile.o 
Python/codecs.o Python/dynamic_annotations.o Python/dtrace_stubs.o 
Python/errors.o Python/frozenmain.o Python/future.o Python/getargs.o 
Python/getcompiler.o Python/getcopyright.o Python/getplatform.o 
Python/getversion.o Python/graminit.o Python/import.o Python/importdl.o 
Python/marshal.o Python/modsupport.o Python/mystrtoul.o Python/mysnprintf.o 
Python/peephole.o Python/pyarena.o Python/pyctype.o Python/pyfpe.o 
Python/pyhash.o Python/pylifecycle.o Python/pymath.o Python/pystate.o 
Python/pythonrun.o Python/pytime.o Python/random.o Python/structmember.o 
Python/symtable.o Python/sysmodule.o Python/traceback.o Python/getopt.o 
Python/pystrcmp.o Python/pystrtod.o Python/pystrhex.o Python/dtoa.o 
Python/formatter
 _unicode.o Python/fileutils.o Python/dynload_shlib.o   Python/thread.o  
Modules/config.o Modules/getpath.o Modules/main.o Modules/gcmodule.o 
Modules/_threadmodule.o  Modules/posixmodule.o  Modules/errnomodule.o  
Modules/pwdmodule.o  Modules/_sre.o  Modules/_codecsmodule.o  
Modules/_weakref.o  Modules/_functoolsmodule.o  Modules/_operator.o  
Modules/_collectionsmodule.o  Modules/itertoolsmodule.o  Modules/atexitmodule.o 
 Modules/signalmodule.o  Modules/_stat.o  Modules/timemodule.o  
Modules/_localemodule.o  Modules/_iomodule.o Modules/iobase.o Modules/fileio.o 
Modules/bytesio.o Modules/bufferedio.o Modules/textio.o Modules/stringio.o  
Modules/zipimport.o  Modules/faulthandler.o  Modules/_tracemalloc.o 
Modules/hashtable.o  Modules/symtablemodule.o  Modules/xxsubtype.o -lpthread 
-ldl  -lutil -lrt   -lm  
Python/dtrace_stubs.o: In function `PyDTrace_LINE':
Include/pydtrace.h:28: multiple definition of `PyDTrace_LINE'
Python/ceval.o:Include/pydtrace.h:28: first defined here
Python/dtrace_stubs.o: In function `PyDTrace_FUNCTION_ENTRY':
Include/pydtrace.h:29: multiple definition of `PyDTrace_FUNCTION_ENTRY'
Python/ceval.o:Include/pydtrace.h:29: first defined here
Python/dtrace_stubs.o: In function `PyDTrace_FUNCTION_RETURN':
Include/pydtrace.h:30: multiple definition of `PyDTrace_FUNCTION_RETURN'
Python/ceval.o:Include/pydtrace.h:30: first defined here
Python/dtrace_stubs.o: In function `PyDTrace_GC_START':
Include/pydtrace.h:31: multiple definition of `PyDTrace_GC_START'
Python/ceval.o:Include/pydtrace.h:31: first defined here
Python/dtrace_stubs.o: In function `PyDTrace_GC_DONE':
Include/pydtrace.h:32: multiple definition of `PyDTrace_GC_DONE'
Python/ceval.o:Include/pydtrace.h:32: first defined here
Python/dtrace_stubs.o: In function `PyDTrace_INSTANCE_NEW_START':
Include/pydtrace.h:33: multiple definition of `PyDTrace_INSTANCE_NEW_START'
Python/ceval.o:Include/pydtrace.h:33: first defined here
Python/dtrace_stubs.o: In function `PyDTrace_INSTANCE_NEW_DONE':
Include/pydtrace.h:34: multiple definition of `PyDTrace_INSTANCE_NEW_DONE'

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

[Berker Peksag]

Changes by Berker Peksag :


--
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Mariatta Wijaya]

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24363] httplib fails to handle semivalid HTTP headers

[Martin Panter]

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10765] Build regression from automation changes on windows

[Zachary Ware]

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 tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24363] httplib fails to handle semivalid HTTP headers

[Roundup Robot]

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Masayuki Yamamoto]

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_dirs

After that I searched Makefile rule for installing $(LDLIBRARY) into 
"$(prefix)/lib/python3.5/config-3.5m" to look for way of simplifying code.  And 
I came across the $(LIBPL) configuration variable that is used by installation 
of the configuration for building library.
Hence I made a patch that adds to library_dirs the $(LIBPL) configuration 
variable instead of the "$(prefix)/lib/python$(VERSION)/config".  I succeeded 
to build '_speedups' C extension module of simplejson using new python that is 
applied this patch.
Erik, Would you be able to verify this patch?
Thanks

Build log:
$ patch -p1 <3.5-issue27374-distutils-build_ext.patch
$ ./configure --prefix=/opt/py35 --with-threads --with-dbmliborder=gdbm 
--with-system-ffi --with-system-expat
$ make touch && make -j2 && make altinstall
$ /opt/py35/bin/python3.5 -V
Python 3.5.2+
$ LANG=C /opt/py35/bin/pip3.5 install -v simplejson
(snip)
running build_ext
building 'simplejson._speedups' extension
creating build/temp.cygwin-2.6.0-i686-3.5
creating build/temp.cygwin-2.6.0-i686-3.5/simplejson
gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall 
-Wstrict-prototypes -I/opt/py35/include/python3.5m -c simplejson/_speedups.c -o 
build/temp.cygwin-2.6.0-i686-3.5/simplejson/_speedups.o
gcc -shared -Wl,--enable-auto-image-base 
build/temp.cygwin-2.6.0-i686-3.5/simplejson/_speedups.o 
-L/opt/py35/lib/python3.5/config-3.5m -L/opt/py35/lib -lpython3.5m -o 
build/lib.cygwin-2.6.0-i686-3.5/simplejson/_speedups.cpython-35m.dll
running install_lib
(snip)

--
Added file: 
http://bugs.python.org/file44685/3.5-issue27374-distutils-build_ext.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28128] Improve the warning message for invalid escape sequences

[Nick Coghlan]

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 code doing the compilation rather than 
to the code containing the offending (non-)escape sequence.

That's making it difficult for folks to act effectively on the warnings when 
they receive them, and also poses problems for correctly filtering out warnings 
coming from code in dependencies rather than an application's own code.

--
nosy: +eric.smith

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Martin Panter]

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 
more info why the Free BSD build could not find Python/Python-ast.c, or Roumen 
can get back with more info. Closing for the moment, but I am happy to help if 
I can resolve any problems that remain.

--
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28128] Improve the warning message for invalid escape sequences

[Emanuel Barry]

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.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28128] Improve the warning message for invalid escape sequences

[Nick Coghlan]

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 to complain about unrecognised ones, as it doesn't have the ability 
to report the appropriate context for where the offending string exists in the 
code base (hence this issue report, and the misattribution problem in the 
generated warning).

Instead, you probably want to look at delaying generation of the error until 
the point where AST Bytes and Str nodes are being generated for inclusion in 
the AST, as at that point the code generator has access to full file, line, and 
column information regarding the location of the problematic escape.

However, I also expect you'll run into a problem where you'll need to be able 
to embed *something* in the processed string that lets the latter stage of the 
pipeline detect that there was an unknown escape rather than a properly escaped 
usage of "\\" (which is presumably why the "immediate warning" approach was 
attempted first - it doesn't need that ability to communicate with the latter 
stage of the pipeline).

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue27348] traceback (and threading) drops exception message

[Martin Panter]

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28128] Improve the warning message for invalid escape sequences

[Nick Coghlan]

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" > escape_warning.py
$ ./python -W all escape_warning.py 
_frozen_importlib:205: DeprecationWarning: invalid escape sequence '\d'
\d

That's a misattribution - the warning should be reported against the module 
being imported, not against the import system itself.

Compare that to the attribution of the old SyntaxWarning for assignments prior 
to a scope declaration:

$ cat syntax_warning.py 
def f():
x = 1
global x
$ python3 -c "import syntax_warning" 
/home/ncoghlan/devel/py36/syntax_warning.py:3: SyntaxWarning: name 'x' is 
assigned to before global declaration
  global x

(Run with 3.5, as that became a full SyntaxError for 3.6)

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28128] Improve the warning message for invalid escape sequences

[Yury Selivanov]

Yury Selivanov added the comment:

BTW, this will also help to make warnings more friendly in #26182.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28128] Improve the warning message for invalid escape sequences

[Emanuel Barry]

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, however (AFAIK) strings aren't checked again once 
they've been created; they're assumed to be correct (and checking them at 
runtime would presumably add a performance hit to *all* strings, which I think 
is too big a price to pay).

On the other hand, a way to ignore invalid escapes in certain files could be 
considered, but we need to be somewhat careful since some people might choose 
to silence all warnings, thus defeating the purpose.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Martin Panter]

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 would be to clarify that for existing versions 2.7, 3.5, etc, that 
the constructor arguments are _not_ ignored and should correspond to the file 
descriptor. Then in the next Python version we can make it more automatic using 
the getsockopt() techniques.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28139] Misleading Indentation in C source code

[Martin Panter]

Changes by Martin Panter :


Added file: http://bugs.python.org/file44684/indent.py3.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28139] Misleading Indentation in C source code

[Martin Panter]

Changes by Martin Panter :


Added file: http://bugs.python.org/file44683/indent.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28143] ASDL compatibility with Python 3 system interpreter

[Martin Panter]

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.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28128] Improve the warning message for invalid escape sequences

[Nick Coghlan]

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 period already - if we couldn't effectively respond 
to this kind of pre-release usability feedback, the beta period would be 
nowhere near as effective.

Ideally, this would also let you hook into the same system that ensures syntax 
warnings are correctly attributed to the code containing them from a warning 
filter perspective, rather than the import statement triggering the 
compilation. One possible way to do that would be to postpone generating this 
error to a later stage of the code generation pipeline rather than doing it 
directly in the parser.

Otherwise folks trying to constrain "-Werror" to just their own code and not 
their dependencies are going to have a bad time of it. If we find we can't 
readily fix that aspect of the change, then I'd go so far as proposing to 
revert it and trying again for 3.7. If we do find we need to take that step, we 
could still encourage linter developers to start complaining about unknown 
escapes during the 3.6 cycle.

P.S. As general background, the "No new features after beta 1" rule is more 
accurately written as "No new features after beta 1, *except* for features 
needed to resolve usability problems reported with changes that already landed 
in beta 1". The biggest one of those I've seen was the PEP 492 implementation 
for 3.5, where the implementation data model was originally still just 
"generators with a particular flag set" (similar to the 3.4 model), but the 
Tornado and Cython folks found that unworkable after the beta went out, so we 
made both the Python API and C API expose them as distinct classes with 
different attributes (cr_* instead of gi_*) and different ABCs that the asyncio 
checked for.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28139] Misleading Indentation in C source code

[Martin Panter]

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 -> open

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28143] ASDL compatibility with Python 3 system interpreter

[R. David Murray]

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28143] ASDL compatibility with Python 3 system interpreter

[Martin Panter]

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 Python 3 support. But even that seems risky.

Your changes obviously make the files incompatible with Python 2:

print()  # Prints an empty tuple
print("Error visiting", repr(object))  # Prints a 2-tuple
f = open(p, "w")  # Writes CRLFs on Windows (I think; it’s been a while)

If we do go down this road, it may be worth looking at what has already been 
done to the corresponding scripts in Python 3.

But you may not actually need to regenerate the files. If you are building from 
the source directory, try “make touch” after generating the makefile. In 
general, try “touch Include/Python-ast.h Python/Python-ast.c”.

I would like to see this be made easier for both Python 2 and 3. I suggested 
some other ideas in Issue 23404.

--
nosy: +martin.panter

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24366] Simple indentation

[Roundup Robot]

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28145] Fix whitespace in C source code

[Roundup Robot]

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/02dd99aeba7d

New changeset 87de1f12c41c by Martin Panter in branch '3.6':
Issue #28145: Merge spelling fixes from 3.5 into 3.6
https://hg.python.org/cpython/rev/87de1f12c41c

New changeset 4a35699e7b05 by Martin Panter in branch 'default':
Issue #28145: Merge spelling fixes from 3.6
https://hg.python.org/cpython/rev/4a35699e7b05

--
nosy: +python-dev

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Matthew Barnett]

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 tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1284316] Win32: Security problem with default installation directory

[Samuel Bronson]

Samuel Bronson added the comment:

Um, you know this still affects Python 2.7 right?

Yes, I realize that it's not going to be very practical to change the default 
installation path for 2.7, but that doesn't make the issue disappear, nor is 
that the only way to close the hole.

Which is to say, the 2.7 installer should be changed to tighten the permissions 
on the installation directory when doing an "all-users" install (even if the 
directory already exists, though in that case it might make sense for it to be 
optional).

(I suppose the same logic applies to any other version < 3.5 that's still 
getting security updates, too?)


P.S. Does this count as CVE-2012-5379, even though that was reported against 
ActiveState's distribution?

I'm pretty sure it's an instance of CWE-276 
, at any rate.

--
nosy: +SamB
versions: +Python 2.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Tim Graham]

Tim Graham added the comment:

Adding an updated patch.

I guess the (?i:CaseInsensitive) syntax isn't merged yet? I tried it but it 
didn't work. It might be premature to proceed with this deprecation if that 
alternative isn't already present. Is there an issue for it?

--
Added file: http://bugs.python.org/file44680/better-warning-2.diff

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28158] Implement LOAD_GLOBAL opcode cache

[STINNER Victor]

STINNER Victor added the comment:

Can you please post results of the performance benchmark suite?

If you give me more time, I can review the patch.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28128] Improve the warning message for invalid escape sequences

[Emanuel Barry]

Emanuel Barry added the comment:

There definitely needs to be a better message for that. The problem is that the 
parser doesn't have access to the whole string (of course; it's being 
constructed!), so I think there are several possible venues here:

- Change DeprecationWarning to display the line which is faulty (unlikely);
- Promote these specific warnings to SyntaxErrors *only* if the warning is an 
error (i.e. Python was run with -W error), in which case the compilation of 
code is stopped either way, so there is no drawback (but only being a syntax 
error "sometimes" is likely to confuse people);
- Use a different warning class, but presumably we'd need a new one and we 
can't do that now since we're in beta (unless Ned thinks this is appropriate, 
but I doubt it).

Anything else, maybe? I'm sure there is a way to properly fix it; my personal 
favourite all things considered is the second option (which I've thought over 
and over recently), but I'm open to other, less intrusive alternatives.

My intention is to make this deprecation the least painful possible for 
application and third-party library developers. As such, I think adding a note 
to the docs (possibly in What's New, but probably also under a few other 
related places) is good, and probably doing a preemptive SO question+answer for 
people who stumble upon this.

I've added to nosy a couple of people whose feedback I believe could be very 
helpful.

--
nosy: +brett.cannon, ncoghlan, rhettinger, yselivanov

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28158] Implement LOAD_GLOBAL opcode cache

[Yury Selivanov]

Yury Selivanov added the comment:

I'm going to commit this patch tomorrow.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26797] Segafault in _PyObject_Alloc

[STINNER Victor]

STINNER Victor added the comment:

> Closing this one. Haven't seen this in a while, probably it was a bug in 
> libuv.

I told you so! :-D

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26797] Segafault in _PyObject_Alloc

[Yury Selivanov]

Yury Selivanov added the comment:

Closing this one. Haven't seen this in a while, probably it was a bug in libuv.

--
resolution:  -> works for me
stage: test needed -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue27386] Asyncio server hang when clients connect and immediately disconnect

[Yury Selivanov]

Yury Selivanov added the comment:

It looks like this was fixed by #27759!.  Jim, could you please verify?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28128] Improve the warning message for invalid escape sequences

[Tim Graham]

Tim Graham added the comment:

I hope the message can be improved for Python 3.6 as the warnings I see when 
running Django's test suite are rather useless to help find and fix the issues:

cpython/Lib/importlib/_bootstrap.py:205: DeprecationWarning: invalid escape 
sequence '\:'

Grepping for these characters patterns to try to figure out where they come 
from is quite difficult.

I did track down one instance in a docstring:
https://github.com/django/django/blob/82f8996785751c413e3b4ac12bf387f781c200d8/django/contrib/gis/maps/google/__init__.py#L41

Is the correct resolution to add an r prefix to the string? It could be nice if 
the release notes contained some guidance on that.

--
nosy: +Tim.Graham

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue27759] selectors incorrectly retain invalid file descriptors

[Yury Selivanov]

Yury Selivanov added the comment:

I've fixed the remaining review comments & committed the patch.  Thank you Mark!

BTW, this also fixes http://bugs.python.org/issue27386.

--
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue27759] selectors incorrectly retain invalid file descriptors

[Roundup Robot]

Roundup Robot added the comment:

New changeset 8944fd09b9ca by Yury Selivanov in branch '3.5':
Issue #27759: Fix selectors incorrectly retain invalid file descriptors.
https://hg.python.org/cpython/rev/8944fd09b9ca

New changeset 08a75f380699 by Yury Selivanov in branch '3.6':
Merge 3.5 (issue #27759)
https://hg.python.org/cpython/rev/08a75f380699

New changeset ded64b96a4e7 by Yury Selivanov in branch 'default':
Merge 3.6 (issue #27759)
https://hg.python.org/cpython/rev/ded64b96a4e7

--
nosy: +python-dev

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue27806] 2.7 32-bit builds fail on future releases of OS X due to dependency on deleted header file

[Alexander Belopolsky]

Alexander Belopolsky added the comment:

> didn't find any existing place to put it into. Any suggestions?

I would put it in Include/pymacconfig.h.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10213] tests shouldn't fail with unset timezone

[Alexander Belopolsky]

Changes by Alexander Belopolsky :


--
resolution:  -> out of date
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue27806] 2.7 32-bit builds fail on future releases of OS X due to dependency on deleted header file

[sashk]

sashk added the comment:

> You should really have a central config

I planned to, but didn't find any existing place to put it into. Any 
suggestions?  

I'll provide updated version of the patch sometime tomorrow.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue27806] 2.7 32-bit builds fail on future releases of OS X due to dependency on deleted header file

[Jeremy Sequoia]

Jeremy Sequoia added the comment:

Correction (bugfix and Tiger-compat):

#if __has_include()
#include 
#define APPLE_SUPPORTS_QUICKTIME (__MAC_OS_X_VERSION_MAX_ALLOWED < 101200) && 
!__LP64__
#else
#define APPLE_SUPPORTS_QUICKTIME !__LP64__
#endif

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue19502] Wrong time zone offset, when using time.strftime() with a given struct_time

[Alexander Belopolsky]

Changes by Alexander Belopolsky :


--
resolution:  -> out of date
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue15941] Time module: effect of time.timezone change

[Alexander Belopolsky]

Alexander Belopolsky added the comment:

Closing in favor of #28157.

--
status: open -> closed
superseder:  -> Document time module constants (timezone, tzname, etc.) as 
deprecated.

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9334] argparse does not accept options taking arguments beginning with dash (regression from optparse)

[paul j3]

paul j3 added the comment:

Clint, the problem is the argparse uses different argument allocation method 
than optparse.

optparse gives the '--subscipt_args` Action all of the remaining strings, and 
says - 'consume what you want, and return the rest'.  So you consume up to (and 
including) the '--'.  Then optparse continues with the rest.

argparse performs the double pass described earlier, and allocates strings to 
each Action based on the larger context.  It gives as many as the Action's 
nargs requires, but tries in various ways to reserve strings for other Actions. 
 Individual Actions never see the big picture.

So the 'REMAINDER' action has to be last (with this '--' positional exception). 
 Your users will have to use the other flags Actions first.

One alternative comes to mind:

- omit the final positional
- use parse_known_args instead of parse_args

Then the 'extras' list will be something like:  ['--', '--verbose'], which you 
can handle in another parser.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue27400] Datetime NoneType after calling Py_Finalize and Py_Initialize

[Christian Heimes]

Christian Heimes added the comment:

Wouldn't it clear strptime_module when a subinterpreter shuts down, too? It's 
not a big deal because it can't cause a crash.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24780] difflib.ndiff produces unreadable output when input missing trailing newline

[Adrian Chan]

Adrian Chan added the comment:

I've attached a potential fix for this issue.

While trying to fix this, I noticed that I coudn't assume that I just need to 
ensure that each line has a newline. If I always ensure each line in diffline 
has a newline, then the fourth test in testAssertMultilineEqual (in 
Lib/unittest/test/test_assertions.py) fails because standardMsg in 
assertMultiLineEqual in Lib/unittest/case.py is just one line without a 
newline. To sidestep this problem, I made it so that I only ensure there is a 
newline for each line if and only if there is more than one line in difflines. 
However, I'm not sure that I can assume there should be a newline in cases 
similar to the fourth test (where longMessage is set to true and a 'msg' is 
passed) in testAssertMultilineEqual but where there is more than one line in 
standardMsg in assertMultiLineEqual.

--
Added file: http://bugs.python.org/file44679/fix_24780.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue27377] Add smarter socket.fromfd()

[Christian Heimes]

Christian Heimes added the comment:

I opened #28134 because I was running into a similar issue with 
socket.socket(fileno). Since this new feature didn't make it into 3.6, can we 
at least change the constructor of socket.socket() to set a correct family, 
type and proto?

Any fix is better than no fix. It doesn't have to work for all socket types on 
all operating systems. The feature is mostly used for socket inheritance, 
systemd socket activation or fd transfer over Unix sockets of AF_INET, AF_INET6 
and AF_UNIX file descriptors.

--
nosy: +christian.heimes
versions: +Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue27400] Datetime NoneType after calling Py_Finalize and Py_Initialize

[Alexander Belopolsky]

Alexander Belopolsky added the comment:

Yes, I think something like the attached patch may do the trick.

--
assignee:  -> belopolsky
keywords: +patch
versions: +Python 3.6, Python 3.7 -Python 3.5
Added file: http://bugs.python.org/file44678/issue27400.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Roundup Robot]

Roundup Robot added the comment:

New changeset 8550ab528a31 by Yury Selivanov in branch '3.5':
Issue #28176: Fix callbacks race in asyncio.SelectorLoop.sock_connect.
https://hg.python.org/cpython/rev/8550ab528a31

New changeset 3d8ba65a0054 by Yury Selivanov in branch '3.6':
Merge 3.5 (issue #28176)
https://hg.python.org/cpython/rev/3d8ba65a0054

New changeset 5024e2a82181 by Yury Selivanov in branch 'default':
Merge 3.6 (issue #28176)
https://hg.python.org/cpython/rev/5024e2a82181

--
nosy: +python-dev

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Yury Selivanov]

Changes by Yury Selivanov :


--
resolution:  -> fixed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Yury Selivanov]

New submission from Yury Selivanov:

Proxy issue for https://github.com/python/asyncio/pull/366

--
assignee: yselivanov
components: asyncio
messages: 276628
nosy: gvanrossum, yselivanov
priority: normal
severity: normal
stage: resolved
status: open
title: Fix callbacks race in asyncio.SelectorLoop.sock_connect
type: behavior
versions: Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue27415] regression: BaseEventLoop.create_server does not accept port=None

[Yury Selivanov]

Yury Selivanov added the comment:

Looks like this is fixed now.

--
resolution:  -> works for me
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue27400] Datetime NoneType after calling Py_Finalize and Py_Initialize

[Christian Heimes]

Christian Heimes added the comment:

PEP 3121 is a big change. Can we use PyModuleDef->m_clear() for a clever hack?

--
nosy: +christian.heimes

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue27665] Make create_server able to listen on several ports

[Yury Selivanov]

Yury Selivanov added the comment:

I think this has been already fixed.  Please reopen if I missed something.

--
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26050] Add new StreamReader.readuntil() method

[Yury Selivanov]

Yury Selivanov added the comment:

Looks like we already have docs for readuntil.  Mark, could you please check if 
we have some docs missing (or just close the issue)?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue27929] asyncio.AbstractEventLoop.sock_connect broken for AF_BLUETOOTH

[Yury Selivanov]

Yury Selivanov added the comment:

I'm not sure this is still relevant for the latest asyncio in 3.6.  Robert, 
could you please test if this is still the case?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue27400] Datetime NoneType after calling Py_Finalize and Py_Initialize

[Alexander Belopolsky]

Alexander Belopolsky added the comment:

I am not sure this is possible to fix without refactoring the datetime module 
according to PEP 3121. See #15390.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28160] Python -V and --version output to stderr instead of stdout

[Barry A. Warsaw]

Changes by Barry A. Warsaw :


--
nosy: +barry

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

In tests you can either add re.escape(), or escape special characters manually 
(r'\(\?i\)'). What you prefer.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

Thanks Tim, this is great idea! I consider this as usability bug and going to 
apply a fix to 3.6.

But regular expression can be generated and be very long. I think it should be 
truncated before including in a warning message.

As for Django, you can use (?i:CaseInsensitive) in 3.7 (unless _prefix is case 
sensitive, but you want to make it case sensitive if pattern is case sensitive).

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26909] Asyncio: Pipes and socket IO is very slow

[Yury Selivanov]

Yury Selivanov added the comment:

Closing this one.  Thank you Mark for discovering the issue and suggesting a 
solution (still hope we'll commit your patch in 3.7).

Thank you INADA Naoki for the patch!

--
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26909] Asyncio: Pipes and socket IO is very slow

[Roundup Robot]

Roundup Robot added the comment:

New changeset e6adc2448c3d by Yury Selivanov in branch '3.5':
Issue #26909: Fix slow pipes IO in asyncio.
https://hg.python.org/cpython/rev/e6adc2448c3d

New changeset c462db8985d8 by Yury Selivanov in branch '3.6':
Merge 3.5 (asyncio, issue #26909)
https://hg.python.org/cpython/rev/c462db8985d8

New changeset 6b07f261ccf4 by Yury Selivanov in branch 'default':
Merge 3.6 (asyncio, issue #26909)
https://hg.python.org/cpython/rev/6b07f261ccf4

--
nosy: +python-dev

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24510] Make _PyCoro_GetAwaitableIter a public API

[Yury Selivanov]

Yury Selivanov added the comment:

Closing this one as no one has requested this for 2 years.

--
resolution:  -> wont fix
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24511] Add methods for async protocols

[Yury Selivanov]

Yury Selivanov added the comment:

I think we can close this one.

--
resolution:  -> wont fix
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26858] android: setting SO_REUSEPORT fails

[Yury Selivanov]

Yury Selivanov added the comment:

This issue was fixed in #28174.

--
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
resolution: fixed -> 
stage: resolved -> patch review
status: closed -> open

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue27806] 2.7 32-bit builds fail on future releases of OS X due to dependency on deleted header file

[ppperry]

Changes by ppperry :


--
type:  -> compile error

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28165] The 'subprocess' module leaks roughly 4 KiB of memory per call

[ppperry]

Changes by ppperry :


--
type:  -> resource usage

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue27391] server_hostname should only be required when checking host names

[Jim Fulton]

Jim Fulton added the comment:

SSL is used for more than just HTTP.  The are applications in which clients 
have server public keys that they use to authenticate servers rather than using 
certificate authorities.  For these applications, server host names are 
irrelevant.  This is why it makes sense to have an option on the SSL context to 
disable host name checking.  Removing this ability would break some 
applications.

If the option to check host names is provided as false on the SSL context, it 
makes no sense to check whether the host name, which isn't going to be used, is 
not None.  It's just silly, but not a huge deal one way or the other, because 
there are actually *two* ways to disable host name checking; you can also pass 
'' as the hostname, which is why this isn't a big deal and why I haven't gotten 
around to making a PR yet.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue27806] 2.7 32-bit builds fail on future releases of OS X due to dependency on deleted header file

[Jeremy Sequoia]

Jeremy Sequoia added the comment:

AvailabilityMacros.h is super deprecated and should not be used by anything 
current. Availability.h was added as replacement in 10.5.

__MAC_OS_X_VERSION_MAX_ALLOWED should be checked instead of defined 
(DEPRECATED_IN_MAC_OS_X_VERSION_10_12_AND_LATER)

You should really have a central config and use that instead. Eg:

#include 
#define APPLE_SUPPORTS_QUICKTIME (__MAC_OS_X_VERSION_MAX_ALLOWED < 101200) || 
!__LP64__

Then use APPLE_SUPPORTS_QUICKTIME throughout.  That avoids tons of churn 
whenever things change (as exemplified by this very bug)

--
nosy: +jeremyhu

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24780] difflib.ndiff produces unreadable output when input missing trailing newline

[ppperry]

Changes by ppperry :


--
components:  -Tests
title: unittest assertEqual difference output foiled by newlines -> 
difflib.ndiff produces unreadable output when input missing trailing newline

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28175] Spam

[Zachary Ware]

Changes by Zachary Ware :


--
Removed message: http://bugs.python.org/msg276612

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28175] Spam

[Zachary Ware]

Changes by Zachary Ware :


--
hgrepos:  -355

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28175] Spam

[Zachary Ware]

Changes by Zachary Ware :


--
components:  -Build
nosy:  -himanshu jha
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed
title: @^@^@^@1~8.5.5.7.0.9~2847 Lexmark P.r.i.n.t.e.r  T.e.h S.u.p.p.O.r.T 
P.h.o.n.e n.u.m.b.e.r Lexmark p.h.o.n.e N.u.m.b.e.r. -> Spam
type: performance -> 
versions:  -Python 3.5

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28175] @^@^@^@1~8.5.5.7.0.9~2847^^^^ Lexmark P.r.i.n.t.e.r T.e.h S.u.p.p.O.r.T P.h.o.n.e n.u.m.b.e.r Lexmark p.h.o.n.e N.u.m.b.e.r.

[himanshu jha]

New submission from himanshu jha:

((moti))Call @@@++ USA I8557O92847 LEXMARK p.r.i.n.t.e.r t.e.c.h s.u.p.p.o.r.t 
p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l LEXMARK h.e.l.p d.e.s.k n.u.m.b.e.r 
n.u.m.b.e.r C.a.n.a.d.a LEXMARK s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa USA 1 
I8557O92847 LEXMARK p.r.i.n.t.e.r t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r 
u.s.a. C.a.l.l LEXMARK h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a 
LEXMARK s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa canada 1-1855-709-2847 USA, 
LEXMARK printer Tech Support phone number,LEXMARK technical support phone 
number 1 I8557O92847 .LEXMARK Tech Support Number LEXMARK Tech LEXMARK tech 
support, LEXMARK tech support number, LEXMARK tech support phone number, 
LEXMARK technical support, LEXMARK technical support number, LEXMARK technical 
support phone number, LEXMARK tech support number, LEXMARK support number, 
LEXMARK Tech support phone number, LEXMARK support phone number, LEXMARK 
technical support phone number, LEXMARK technical support number,Support Phone 
Number for LEX
 MARK printer Phone Number for LEXMARK CustomerService Technical Support 
Telephone Number LEXMARK printer support number LEXMARK LEXMARK printer tech 
support number LEXMARK LEXMARK printer technical support number LEXMARK LEXMARK 
printer technical support phone number LEXMARK LEXMARK printer customer service 
number LEXMARK LEXMARK internet security technical support LEXMARK technical 
support phone number LEXMARK LEXMARK tech support phone number LEXMARK LEXMARK 
customer support phone number I-855-709-2847 LEXMARK LEXMARK printer support 
phone number LEXMARK LEXMARK support phone LEXMARK tech support LEXMARK 
customer support LEXMARK phone support LEXMARK support number LEXMARK LEXMARK 
technical support LEXMARK printer customer support phone number LEXMARK LEXMARK 
printer tech support phone number LEXMARK contact LEXMARK support LEXMARK 
printer technical support phone number ~!~I8557092847++ LEXMARK LEXMARK phone 
number LEXMARK tech support LEXMARK support ticket LEXMARK customer suppo
 rt number LEXMARK LEXMARK tech support number LEXMARK LEXMARK technical 
support number LEXMARK LEXMARK support center LEXMARK telephone support call 
LEXMARK support LEXMARK printer support support LEXMARK LEXMARK billing support 
LEXMARK printer technical support number LEXMARK support LEXMARK printer 
LEXMARK online support LEXMARK contact support LEXMARK printer support number 
LEXMARK LEXMARK printer customer support number LEXMARK LEXMARK printer tech 
support number LEXMARK support for LEXMARK LEXMARK phone number LEXMARK LEXMARK 
customer service phone number LEXMARK LEXMARK contact phone number LEXMARK 
LEXMARK printer phone number LEXMARK LEXMARK printer customer service phone 
number LEXMARK phone number LEXMARK for LEXMARK customer service LEXMARK 
software phone number LEXMARK phone number LEXMARK for LEXMARK LEXMARK customer 
service telephone number LEXMARK LEXMARK helpline phone number LEXMARK LEXMARK 
contact number LEXMARK LEXMARK customer service number LEXMARK LEXMARK custom
 er service phone number ~!~I8557092847++ LEXMARK us LEXMARK customer service 
phone number LEXMARK usa LEXMARK telephone number LEXMARK LEXMARK phone number 
LEXMARK usa LEXMARK printer contact number LEXMARK LEXMARK number LEXMARK 
LEXMARK contact number LEXMARK usa LEXMARK printer helpline number LEXMARK 
LEXMARK helpline number LEXMARK LEXMARK customer number LEXMARK LEXMARK printer 
customer service number LEXMARK LEXMARK contact telephone number LEXMARK 
contact number LEXMARK for LEXMARK LEXMARK software contact number LEXMARK 
LEXMARK toll free number LEXMARK LEXMARK telephone number LEXMARK uk LEXMARK 
registration number LEXMARK LEXMARK toll free number LEXMARK usa LEXMARK 
customer service LEXMARK software customer service contact LEXMARK customer 
service LEXMARK customer service phone LEXMARK printer customer service LEXMARK 
service LEXMARK printer technical support LEXMARK printer customer support 
LEXMARK technical support reviews telephone LEXMARK printer LEXMARK tech 
support ph
 one number LEXMARK LEXMARK printer tech support phone number LEXMARK LEXMARK 
printer customer service LEXMARK technical support phone number LEXMARK LEXMARK 
printer free printer support LEXMARK customer service billing LEXMARK customer 
service email address LEXMARK customer service reviews contact LEXMARK customer 
service LEXMARK tech support number LEXMARK usa LEXMARK printer support number 
LEXMARK LEXMARK printer contact number LEXMARK LEXMARK customer service phone 
number LEXMARK LEXMARK technical support usa LEXMARK technical support number 
LEXMARK LEXMARK tech support phone LEXMARK tech support number LEXMARK LEXMARK 
customer service telephone number LEXMARK LEXMARK printer customer support 
number LEXMARK LEXMARK printer phone number LEXMARK LEXMARK printer online 
support LEXMARK customer service number LEXMARK LEXMARK tech support center 
LEXMARK customer service LEXMARK software 

[issue26654] asyncio is not inspecting keyword arguments of functools.partial

[Yury Selivanov]

Yury Selivanov added the comment:

Merged! Thank you!

--
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26654] asyncio is not inspecting keyword arguments of functools.partial

[Roundup Robot]

Roundup Robot added the comment:

New changeset 4ab64ea31d75 by Yury Selivanov in branch '3.5':
Issue #26654: Inspect functools.partial in asyncio.Handle.__repr__.
https://hg.python.org/cpython/rev/4ab64ea31d75

New changeset 03257f04ee9f by Yury Selivanov in branch '3.6':
Merge 3.5 (issue #26654)
https://hg.python.org/cpython/rev/03257f04ee9f

New changeset 1dbe3addba28 by Yury Selivanov in branch 'default':
Merge 3.6 (issue #26654)
https://hg.python.org/cpython/rev/1dbe3addba28

--
nosy: +python-dev

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28160] Python -V and --version output to stderr instead of stdout

[Yaron Goland]

Yaron Goland added the comment:

Fair enough. Thanks for looking at it!

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28174] asyncio: Handle when SO_REUSEPORT isn't properly supported

[Roundup Robot]

Roundup Robot added the comment:

New changeset c1c247cf3488 by Yury Selivanov in branch '3.5':
Issue #28174: Handle when SO_REUSEPORT isn't properly supported (asyncio)
https://hg.python.org/cpython/rev/c1c247cf3488

New changeset f2fdb624074a by Yury Selivanov in branch '3.6':
Merge 3.5 (issue #28174)
https://hg.python.org/cpython/rev/f2fdb624074a

New changeset e9c37e3efcb2 by Yury Selivanov in branch 'default':
Merge 3.6 (issue #28174)
https://hg.python.org/cpython/rev/e9c37e3efcb2

--
nosy: +python-dev

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28174] asyncio: Handle when SO_REUSEPORT isn't properly supported

[Yury Selivanov]

Changes by Yury Selivanov :


--
resolution:  -> fixed
status: open -> closed
type:  -> enhancement

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28174] asyncio: Handle when SO_REUSEPORT isn't properly supported

[Yury Selivanov]

New submission from Yury Selivanov:

Proxy issue for https://github.com/python/asyncio/pull/418

--
assignee: yselivanov
components: asyncio
messages: 276606
nosy: gvanrossum, yselivanov
priority: normal
severity: normal
stage: resolved
status: open
title: asyncio: Handle when SO_REUSEPORT isn't properly supported
versions: Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28171] getopt.getopt error processing long_options

[Steven D'Aprano]

Steven D'Aprano added the comment:

> argparse here I come!

https://docs.python.org/2/library/argparse.html#argument-abbreviations-prefix-matching

Prefix matching is a standard feature of all command line option parsers 
that I know of.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue27908] del _limbo[self] KeyError

[Maciej Urbański]

Maciej Urbański added the comment:

To address @Dima.Tisnek concern I have changed exception message in case thread 
start process is merely in progress.

I kept `self._started` check under a lock so we can avoid more extreme race 
condition of one thread checking `self._started` right before another sets it 
and exits the limbo.

As for testing `self._started` under a lock, but setting it without one. I'm 
avoiding it only because of performance reasons. The read is super cheap, while 
notification of `.set()` is more complex, so if aesthetics are only reasons for 
doing it there then I would advise against holding that lock while executing it.

Of course I could also do a `self in _active` check under a lock, but that is 
slightly more costly, than `self._started` check and not any more useful.

I may be prematurely optimizing things, but people tend to like they threads to 
startup ASAP.

--
Added file: http://bugs.python.org/file44677/issue27908_2.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28172] Upper-case all example enum members

[Ethan Furman]

Changes by Ethan Furman :


--
nosy: +ethan.furman

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue27400] Datetime NoneType after calling Py_Finalize and Py_Initialize

[Josh Rosenberg]

Josh Rosenberg added the comment:

Hmm... On checking down some of the code paths and realizing there were some 
issues in 3.5 (redundant code, and what looked like two memory leaks), I 
checked tip (to avoid opening bugs on stale code), and discovered that #22557 
rewrote the import code, reducing the cost of top level reimport by ~60%, so my 
microbenchmarks (run on Python 3.5.0) are already out of date for 3.6's faster 
re-import. Even so, caching wasn't a wholly unreasonable optimization before 
now, and undoing it now still has a cost, if a smaller one.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28171] getopt.getopt error processing long_options

[Mike Hagerty]

Mike Hagerty added the comment:

You win.  It's not a bug, it's a feature ... that renders the module
incorrect
by any reasonable definition.

argparse here I come!

On Thu, Sep 15, 2016 at 3:20 PM, Steven D'Aprano 
wrote:

>
> Steven D'Aprano added the comment:
>
> > How is silently failing to resolve input errors okay ?
>
> You haven't demonstrated that it fails to resolve input errors. You have
> demonstrated a *feature*, not a bug: getopt will accept prefixes if they
> unambiguously match ONE long option only. If the prefix matches two or more
> options, then the prefix is ambiguous and getopt will not accept it.
>
> --
>
> ___
> Python tracker 
> 
> ___
>

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28171] getopt.getopt error processing long_options

[Steven D'Aprano]

Steven D'Aprano added the comment:

> How is silently failing to resolve input errors okay ?

You haven't demonstrated that it fails to resolve input errors. You have 
demonstrated a *feature*, not a bug: getopt will accept prefixes if they 
unambiguously match ONE long option only. If the prefix matches two or more 
options, then the prefix is ambiguous and getopt will not accept it.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28172] Upper-case all example enum members

[SilentGhost]

Changes by SilentGhost :


--
stage:  -> patch review

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28173] Misspelled Assert

[Ethan Furman]

Ethan Furman added the comment:

The misspelling is intentional.  That section is talking about what happens 
when an "assert_" method is misspelled.

--
nosy: +ethan.furman, michael.foord
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28114] parse_envlist(): os.execve(), os.spawnve(), etc. crash in Python 3.6.0 when env contains byte strings

[STINNER Victor]

STINNER Victor added the comment:

Ok fine ;-) Let's keep #if defined(HAVE_WEXECV) || defined(HAVE_WSPAWNV).

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28114] parse_envlist(): os.execve(), os.spawnve(), etc. crash in Python 3.6.0 when env contains byte strings

[Steve Dower]

Steve Dower added the comment:

We already use HAVE_WEXECV and HAVE_WSPAWNV elsewhere to choose the wide-char 
versions of these functions. You've got a few changes to make if you want to 
maintain consistency.

Personally I prefer feature flags to platform flags, then let pyconfig.h 
control them, especially when we're not directly using platform-specific APIs.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue27400] Datetime NoneType after calling Py_Finalize and Py_Initialize

[Josh Rosenberg]

Josh Rosenberg added the comment:

Nick: Looks like it's quite a bit more work than just a dict lookup. That 
PyImport_ImportModuleNoBlock call (which seems odd; the implementation of 
NoBlock is just to wrap the blocking function; guess we don't allow 
non-blocking imports anymore and this is just to avoid changing all the names 
elsewhere?) involves a *lot* more work than just a dict lookup (it devolves to 
a PyImport_Import call 
https://hg.python.org/cpython/file/3.5/Python/import.c#l1743 , which basically 
does everything involved in the import process aside from actually 
reading/parsing the file unconditionally, because of how weird __import__ 
overrides can be, I guess).

While it's not a perfect comparison, compare:

>>> import _strptime  # It's now cached

# Cache globals dict for fair comparison without globals() call overhead
>>> g = globals() 

# Reimport (this might be *more* expensive at C layer, see notes below)
>>> %timeit -r5 import _strptime
100 loops, best of 5: 351 ns per loop

# Dict lookup (should be at least a bit cheaper at C layer if done 
equivalently, using GetAttrId to avoid temporary str)
>>> %timeit -r5 g['_strptime']
1000 loops, best of 5: 33.1 ns per loop

# Cached reference (should be *much* cheaper at C layer)
>>> %timeit -r5 _strptime
1 loops, best of 5: 19.1 ns per loop

Note: I'm a little unclear on whether a Python function implemented in C has 
its own globals, or whether it's simulated as part of the C module 
initialization); if it lacks globals, then the work done for PyImport_Import 
looks like it roughly doubles (it has to do all sorts of work to simulate 
globals and the like), so that 351 ns per re-import might actually be costlier 
in C.

Either way, it's a >10x increase in cost to reimport compared to a dict lookup, 
and ~18x speedup over using a cached reference (and like I said, I think the 
real cost of the cheaper options would be much less in C, so the multiplier is 
higher). Admittedly, in tests, empty string calls to `_strptime._strptime` take 
around 7.4 microseconds (with realistic calls taking 8.5-13.5 microseconds), so 
caching is saving maybe a third of a microsecond overhead, maybe 2.5%-4.5% of 
the work involved in the strptime call.

--
nosy: +josh.r

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28171] getopt.getopt error processing long_options

[Steven D'Aprano]

Steven D'Aprano added the comment:

> Surely this isn't intended behavior (?)

It is indeed. That's standard behaviour for GNU getopt, which the Python module 
is modelled after:

[steve@ando ~]$ getopt --version
getopt (enhanced) 1.1.4
[steve@ando ~]$ getopt --versi
getopt (enhanced) 1.1.4

--
nosy: +steven.daprano

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28173] Misspelled Assert

[Chris Rao]

New submission from Chris Rao:

In the second code block in the section on autospeccing in 
https://docs.python.org/3/library/unittest.mock.html#auto-speccing, assert is 
spelled as "assret"

>>> mock = Mock(name='Thing', return_value=None)
>>> mock(1, 2, 3)
>>> mock.assret_called_once_with(4, 5, 6)

--
assignee: docs@python
components: Documentation
messages: 276596
nosy: Chris Rao, docs@python
priority: normal
severity: normal
status: open
title: Misspelled Assert

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28171] getopt.getopt error processing long_options

[SilentGhost]

SilentGhost added the comment:

It's not an error. Read the docs, there's a longer and more detailed 
explanation there. There is no chance of this being changed, not in a module 
like getopt.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com