[issue29587] Generator/coroutine 'throw' discards exc_info state, which is bad

[Chris Jerdonek]

Change by Chris Jerdonek :


--
nosy: +chris.jerdonek

___
Python tracker 

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

[issue18861] Problems with recursive automatic exception chaining

[Chris Jerdonek]

Change by Chris Jerdonek :


--
nosy: +chris.jerdonek

___
Python tracker 

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

[issue29587] Generator/coroutine 'throw' discards exc_info state, which is bad

[Hynek Schlawack]

Change by Hynek Schlawack :


--
nosy: +hynek

___
Python tracker 

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

[issue31997] SSL lib does not handle trailing dot (period) in hostname or certificate

[Hynek Schlawack]

Change by Hynek Schlawack :


--
nosy: +hynek

___
Python tracker 

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

[issue31997] SSL lib does not handle trailing dot (period) in hostname or certificate

[Christian Heimes]

Christian Heimes  added the comment:

After more investigation and discussion with Daniel Stenberg, I'm considering 
to close the issue as WONTFIX + documentation update. The issue cannot be 
addressed in the SSL/TLS layer. I'm waiting for a reply from Ryan Sleevi on CAB 
baseline requirements. BR 1.5.1 does not state if trailing dots are allowed.

The trailing dot issue affects more than just hostname matching. For HTTPS, 
server name indication (SNI) and HTTP "Host" header play an important role, 
too. In general the SNI TLS header and HTTP Host header must match. In case the 
HTTP header is missing or deviates from the SNI header, web servers like Apache 
fail with Bad Request error. In general SNI must also match a SAN dNSName 
extension.

Apache with mod_ssl strips off trailing dots internally. Daniel pointed out 
that other webservers (IIS) do not handle trailing dots correctly. Some 
protocols like SMTP do not allow trailing dot in FQDN.

IMO the problem should be handled in high level libraries such as urllib. 
urllib should use the FQDN with trailing dot for DNS resolution, then strip off 
the trailing dot and use the FQDN for HTTP Host header and server_hostname.

--

___
Python tracker 

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

[issue31975] Add a default filter for DeprecationWarning in __main__

[Antoine Pitrou]

Antoine Pitrou  added the comment:

> * Recommend that test runners also set this in the environment (so it's 
> inherited by subprocesses), not just in the current process

+1

> * Clearly document "-We", "-Wi", "-Wd" as shorthands to override the default 
> warnings filters with universal "error", "ignore" and "default" settings 
> (right now you have to reverse engineer this from the warnings docs)

+1

> * Clearly document "PYTHONWARNINGS=error", "PYTHONWARNINGS=ignore", and 
> "PYTHONWARNINGS=default" as the environmental equivalents (right now you have 
> to reverse engineer this from the warnings docs)

+1

> * Explicitly recommend FutureWarning as the "always visible by default" 
> alternative to DeprecationWarning

That's rather weird.  It seems more and more library authors are
discontent with DeprecationWarning's default behaviour.  Why not change
DeprecationWarning's behaviour to match expectations instead of starting
recommending people switch to something less obvious?

> I suspect if we'd been clearer about our assumptions back when the change was 
> made and advertised in the Python 2.7 What's New, we'd have had fewer 
> problems in the time since

I think the main reason is that our assumptions weren't clear at all.
The people who promoted this change didn't envision the issues that
would come with it.

--

___
Python tracker 

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

[issue31997] SSL lib does not handle trailing dot (period) in hostname or certificate

[Christian Heimes]

Christian Heimes  added the comment:

Ryan said:
Chrome will match both trailing dot and non-trailing dot in URL against 
non-trailing dot in cert. trailing dot in cert is 5280 violation by not being 
in preferred name syntax

https://twitter.com/sleevi_/status/929305281405833216

--
versions: +Python 3.6, Python 3.7 -Python 3.8

___
Python tracker 

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

[issue32002] test_c_locale_coercion fails when the default LC_CTYPE != "C"

[Xavier de Gaye]

Xavier de Gaye  added the comment:

> Several of the tests in test_c_locale_coercion (particularly 
> LocaleCoercionTests._check_c_locale_coercion) tend to assume that the system 
> default locale used when setting setlocale(category, "") and when all the 
> relevant environment variables are empty/blank will be the "C"/"POSIX" locale.
>
> While this is often true POSIX does not require this to be the case.

I think you are right. The section starting with "The values of locale 
categories shall be determined by a precedence order;" in [1] states:

4. If the LANG environment variable is not set or is set to the empty string, 
the implementation-defined default locale shall be used.

In the current implementation of PR 4334 [2] only one change to 
test_c_locale_coercion is needed to fix the failures of some subtests of 
test_PYTHONCOERCECLOCALE_set_to_warn when all the locale envt variables are set 
to the empty string. All the other tests are unchanged and ok because the new 
_Py_SetLocaleFromEnv() function [3] causes Android to behave as a plain *nix 
platform except when the locale envt variables are unset or set to an empty 
string.

[1] http://pubs.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap08.html
[2] PR 4334: Fix the implementation of PEP 538 on Android
[3] And because after calling setlocale(category, "C"), setlocale(category) 
returns "C" on Android (this may not be the case on Cygwin).

--

___
Python tracker 

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

[issue31572] Avoid suppressing all exceptions in PyObject_HasAttr()

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:


New changeset d4f8480dfe89447587550a85b61d4e9faf827e98 by Serhiy Storchaka in 
branch 'master':
bpo-31572: Don't silence unexpected errors in the _warnings module. (#3731)
https://github.com/python/cpython/commit/d4f8480dfe89447587550a85b61d4e9faf827e98


--

___
Python tracker 

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

[issue31572] Avoid suppressing all exceptions in PyObject_HasAttr()

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:


New changeset 1707e4020fa8dca8e6a3ac4f9da105b54d597b66 by Serhiy Storchaka in 
branch 'master':
bpo-31572: Silence only AttributeError when get the __copy__ attribute in 
itertools.tee(). (#3724)
https://github.com/python/cpython/commit/1707e4020fa8dca8e6a3ac4f9da105b54d597b66


--

___
Python tracker 

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

[issue31572] Avoid suppressing all exceptions in PyObject_HasAttr()

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:


New changeset 60c3d3551a96febac7b6016fb44605643842c686 by Serhiy Storchaka in 
branch 'master':
bpo-31572: Get rid of _PyObject_HasAttrId() in dict and OrderedDict. (#3728)
https://github.com/python/cpython/commit/60c3d3551a96febac7b6016fb44605643842c686


--

___
Python tracker 

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

[issue31572] Avoid suppressing all exceptions in PyObject_HasAttr()

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:


New changeset bba2239c17a404fc99524bfbf8126c9b3b7fb343 by Serhiy Storchaka in 
branch 'master':
bpo-31572: Get rid of _PyObject_HasAttrId() in the ASDL parser. (#3725)
https://github.com/python/cpython/commit/bba2239c17a404fc99524bfbf8126c9b3b7fb343


--

___
Python tracker 

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

[issue31993] pickle.dump allocates unnecessary temporary bytes / str

[Olivier Grisel]

Olivier Grisel  added the comment:

Alright, I found the source of my refcounting bug. I updated the PR to include 
the C version of the dump for PyBytes.

I ran Serhiy's microbenchmarks on the C version and I could not detect any 
overhead on small bytes objects while I get a ~20x speedup (and no-memory copy) 
on large bytes objects as expected.

I would like to update the `write_utf8` function but I would need to find a way 
to wrap `const char* data` as a PyBytes instance without making a memory copy 
to be able to pass it to my `_Pickle_write_large_bytes`. I browsed the C-API 
documentation but I could not understand how to do that.

Also I would appreciate any feedback on the code style or things that could be 
improved in my PR.

--

___
Python tracker 

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

[issue30576] http.server should support HTTP compression (gzip)

[Pierre Quentel]

Pierre Quentel  added the comment:

I think I have made all the changes requested in the code review (many thanks 
to the reviewer !).

I see that the Pull Request has been flagged "awaiting core review". With the 
deadline for Python 3.7 coming soon (11 weeks), is there a chance that the 
feature will be added on time ? Is there something I should do or someone I 
should contact for that ?

--

___
Python tracker 

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

[issue32007] nis module fails to build against glibc-2.26

[Mike Gilbert]

New submission from Mike Gilbert :

The nis extension module fails to build against glibc-2.26 with the 
"obsolete-rpc" option disabled.

Downstream bug report: https://bugs.gentoo.org/631488

glibc-2.26 release notes: 
https://sourceware.org/ml/libc-alpha/2017-08/msg00010.html

The nis module is normally skipped since rpcsvc/yp_prot.h will not exist. 
However, if the external "libnsl" package is installed, compilation is 
attempted and fails as given below.

building 'nis' extension
x86_64-pc-linux-gnu-gcc -pthread -fPIC -Wno-unused-result -Wsign-compare 
-DNDEBUG -march=native -O2 -pipe -g -fwrapv -std=c99 -Wextra -Wno-unused-result 
-Wno-unused-parameter -Wno-missing-field-initializers -I./Include -I. 
-I/var/tmp/portage/dev-lang/python-3.6.3/work/Python-3.6.3/Include 
-I/var/tmp/portage/dev-lang/python-3.6.3/work/Python-3.6.3 -c 
/var/tmp/portage/dev-lang/python-3.6.3/work/Python-3.6.3/Modules/nismodule.c -o 
build/temp.linux-x86_64-3.6/var/tmp/portage/dev-lang/python-3.6.3/work/Python-3.6.3/Modules/nismodule.o
/var/tmp/portage/dev-lang/python-3.6.3/work/Python-3.6.3/Modules/nismodule.c:17:21:
 fatal error: rpc/rpc.h: No such file or directory
 #include 
 ^
compilation terminated.

To summarize:

glibc no longer provides rpc/rpc.h or rpcsvc/yp_prot.h. One must install a 
couple of external libraries to provide the same functionality.

The missing rpcsvc/yp_prot.h file can be resolved by installing the "libnsl" 
package, which installs the header where setup.py expects to find it.

The missing rpc/rpc.h file may be provided by the "libtirpc" package, but this 
installs the file under /usr/include/tirpc, which must be added to the include 
path (-I/usr/include/tirpc).

Ideally, pkg-config would be used to find both libnsl and libtirpc.

--
components: Build
messages: 306090
nosy: floppymaster
priority: normal
severity: normal
status: open
title: nis module fails to build against glibc-2.26
type: compile error

___
Python tracker 

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

[issue31829] Portability issues with pickle

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

It is possible to resolve issue with Unicode strings ending with \r. We can add 
a special mark in the stream (a combination of opcodes which is no-op) before 
writing the first Unicode strings ending with \r. If this mark is encountered 
in an input stream, therefore it was saved with new Python version, and ending 
\r can be removed from loaded Unicode strings.

--

___
Python tracker 

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

[issue31993] pickle.dump allocates unnecessary temporary bytes / str

[Antoine Pitrou]

Antoine Pitrou  added the comment:

> I would like to update the `write_utf8` function but I would need to find a 
> way to wrap `const char* data` as a PyBytes instance without making a memory 
> copy to be able to pass it to my `_Pickle_write_large_bytes`. 

You should pass it as a memoryview instead:
https://docs.python.org/3/c-api/memoryview.html#c.PyMemoryView_FromMemory

--

___
Python tracker 

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

[issue29180] skip tests that raise PermissionError in test_os (non-root user on Android)

[Xavier de Gaye]

Change by Xavier de Gaye :


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

[issue29181] skip tests that raise PermissionError in test_tarfile (non-root user on Android)

[Xavier de Gaye]

Change by Xavier de Gaye :


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

[issue29184] skip tests of test_socketserver when bind() raises PermissionError (non-root user on Android)

[Xavier de Gaye]

Change by Xavier de Gaye :


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

[issue29180] skip tests that raise PermissionError in test_os (non-root user on Android)

[Xavier de Gaye]

Change by Xavier de Gaye :


--
pull_requests: +4323

___
Python tracker 

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

[issue32008] Example suggest to use a TLSv1 socket

[Kurt Roeckx]

New submission from Kurt Roeckx :

Here:
https://docs.python.org/3/library/ssl.html#ssl.SSLContext.check_hostname

And here:
https://docs.python.org/2/library/ssl.html#ssl.SSLContext.check_hostname

It uses ssl.PROTOCOL_TLSv1, which is a bad example. Please change it to 
PROTOCOL_SSLv23 or PROTOCOL_TLS.

(Those were the first 2 examples I could find via google on how to create an 
ssl connection using python.)

--
assignee: docs@python
components: Documentation
messages: 306093
nosy: docs@python, kroeckx
priority: normal
severity: normal
status: open
title: Example suggest to use a TLSv1 socket
type: enhancement

___
Python tracker 

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

[issue29181] skip tests that raise PermissionError in test_tarfile (non-root user on Android)

[Xavier de Gaye]

Change by Xavier de Gaye :


--
pull_requests: +4324

___
Python tracker 

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

[issue32009] seg fault when using Cntrl-q keymap to exit app

[Britton Kerin]

New submission from Britton Kerin :

This probably applies to more recent version also.

It may be a readline bug, but I haven't seen it except when using the python 
interface, despite using this same .inputrc file with many different command 
line programs.

I've attached the ~/.inputrc which are required to trigger the problem. 
This simple script will allow the problem to be reproduced:

 #!/usr/bin/python3.4-dbg

 import readline

 input('the_prompt> ')

After launching test.py with the given ~/.inputrc in place, simply type Cntrl-q 
to trigger the seg fault.

Perhaps if this can be confirmed to be a readline issue someone can submit a 
bug report to that project.

Britton

--
components: Library (Lib)
files: the.inputrc
messages: 306094
nosy: Britton Kerin
priority: normal
severity: normal
status: open
title: seg fault when using Cntrl-q keymap to exit app
type: crash
versions: Python 3.4
Added file: https://bugs.python.org/file47259/the.inputrc

___
Python tracker 

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

[issue21149] logging._removeHandlerRef is not threadsafe during interpreter shutdown

[Gregory P. Smith]

Gregory P. Smith  added the comment:


New changeset e84f6d3817ad3d18fdfbb5223b8078606166cea0 by Gregory P. Smith in 
branch '2.7':
[2.7] bpo-21149: Workaround a GC finalization bug in logging. (#4368)
https://github.com/python/cpython/commit/e84f6d3817ad3d18fdfbb5223b8078606166cea0


--

___
Python tracker 

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

[issue21149] logging._removeHandlerRef is not threadsafe during interpreter shutdown

[Gregory P. Smith]

Change by Gregory P. Smith :


--
resolution:  -> fixed
stage: patch review -> commit review
status: open -> closed
type:  -> behavior

___
Python tracker 

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

[issue31975] Add a default filter for DeprecationWarning in __main__

[Nick Coghlan]

Nick Coghlan  added the comment:

Regarding "Why not revert DeprecationWarning to behaving the same as 
FutureWarning?", the rationale is basically the one Brett gave on python-dev 
(which was a restatement of the one that led to the change in python-dev): it's 
genuinely annoying as a Python developer to get deprecation warnings in your 
terminal for things like mypy, pylint, flake8, pip, pipenv, etc.

So we've tried "DeprecationWarning ~= FutureWarning" up until 2.6/3.1, and 
found it overly noisy, mixing up output from the tool itself with warnings 
about the state of the tool's code.

Since then, we've tried "DeprecationWarning ~= PendingDeprecationWarning", and 
found that tilts too far in the other direction (especially with popular test 
runners being yet to follow unittest's lead and switch their default warning 
settings)

The PEP will thus propose a middle-ground that leaves FutureWarning and 
PendingDeprecationWarning alone (so folks can still choose those semantics if 
they prefer them), but tweaks the semantics of DeprecationWarning such that 
common app distribution techniques (the console_scripts and gui_scripts 
entry_points, zipapp, executable packages) will still leave them off by default.

--

___
Python tracker 

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

[issue31975] Add a default filter for DeprecationWarning in __main__

[Nick Coghlan]

Nick Coghlan  added the comment:

As far as documentation goes, there are the amendments I'm considering:

===
exception DeprecationWarning

Base class for warnings about deprecated features. Visible by default for 
APIs called from `__main__` modules and when using the unittest test runner. 
See :exc:`PendingDeprecationWarning` and :exc:`FutureWarning` to emit warnings 
for future backwards incompatible changes with different default visibility.

exception PendingDeprecationWarning

Base class for warnings about features which will be deprecated in the 
future. Hidden by default, even for APIs called from `__main__` modules and 
when using the unittest test runner. See :exc:`DeprecationWarning` and 
:exc:`FutureWarning` to emit warnings for future backwards incompatible changes 
with different default visibility.

exception FutureWarning

Base class for warnings about constructs that will change semantically or 
cease working in the future. Always visible by default, even for code in 
imported modules. See :exc:`PendingDeprecationWarning` and 
:exc:`DeprecationWarning` to emit warnings for future backwards incompatible 
changes with different default visibility.
===

(I'd also add notes on default visibility to the other warning categories - 
ImportWarning, BytesWarning, and ResourceWarning are the other "hidden by 
default" categories)

DeprecationWarning gets the preferred name because it has the semantics we 
think we will like best for that use case (i.e. visible in __main__ and while 
running tests, hidden otherwise), while cross-referencing it with FutureWarning 
and PendingDeprecationWarning makes it clear Python developers are still free 
to opt-in to either the pre-2.7 behaviour or the pre-3.7 behaviour if that's 
what they prefer for the APIs they expose.

--

___
Python tracker 

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

[issue31975] Add a default filter for DeprecationWarning in __main__

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Le 12/11/2017 à 00:41, Nick Coghlan a écrit :
> 
> Regarding "Why not revert DeprecationWarning to behaving the same as 
> FutureWarning?", the rationale is basically the one Brett gave on python-dev 
> (which was a restatement of the one that led to the change in python-dev): 
> it's genuinely annoying as a Python developer to get deprecation warnings in 
> your terminal for things like mypy, pylint, flake8, pip, pipenv, etc.

Why would mypy, flake8 or pip emit DeprecationWarnings?
The original problem was about end-user applications, not specialist
developer tools such as pip or mypy.  Specialist developer tools can
enable whatever warnings filter suits them, and that's what we're
promoting for test runners for instance.

But the problem is that, by silencing warnings in end-user applications
(where those warnings may indeed annoy users), in turn we defeat the
whole point of warnings since the developers of those applications
become ignorant of them.  That's the recurring theme of the whole
discussion thread, and your proposal ignores it.

(and I don't think chastising those application developers because they
don't have good enough test coverage will do much to alleviate the
problem; that's how a lot of software still gets written)

> The PEP will thus propose a middle-ground that leaves FutureWarning and 
> PendingDeprecationWarning alone (so folks can still choose those semantics if 
> they prefer them), but tweaks the semantics of DeprecationWarning such that 
> common app distribution techniques (the console_scripts and gui_scripts 
> entry_points, zipapp, executable packages) will still leave them off by 
> default.

Did someone like Nathaniel confirm that the change you're proposing
would satisfy his use cases?  If not, I don't think you're achieving
anything useful here.

--

___
Python tracker 

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

[issue31975] Add a default filter for DeprecationWarning in __main__

[Nick Coghlan]

Nick Coghlan  added the comment:

Antoine, I'm a user too, and this single small change will be enough to
solve *my* problems, while still addressing Guido's developer tool
usability concerns that prompted him to change the default in the first
place (see the stdlib-sig thread for more info on that).

If someone else wants a different change, they can write their own
competing PEP that explains why they think mine would be worse than the
status quo.

--

___
Python tracker 

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

[issue29587] Generator/coroutine 'throw' discards exc_info state, which is bad

[Guido van Rossum]

Guido van Rossum  added the comment:

Yury do you agree this is a bug? Do you have any ideas on how to fix it?

--
nosy: +gvanrossum, yselivanov

___
Python tracker 

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

[issue32009] seg fault when using Cntrl-q keymap to exit app

[Martin Panter]

Martin Panter  added the comment:

This looks the same as Issue 25259. The trigger is that multiple lines are 
generated at the same time, but Python only expects the first line.

--
nosy: +martin.panter
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> readline macros can segfault Python

___
Python tracker 

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

[issue31975] Add a default filter for DeprecationWarning in __main__

[Nick Coghlan]

Nick Coghlan  added the comment:

The initial draft of the PEP is up: https://www.python.org/dev/peps/pep-0565/

--

___
Python tracker 

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

[issue31975] Add a default filter for DeprecationWarning in __main__

[R. David Murray]

R. David Murray  added the comment:

> Why would mypy, flake8 or pip emit DeprecationWarnings?

Because they use python features that get deprecated, and the python the user 
is using to run them gets upgraded.  Now, those particular tools probably will 
get updated quickly, but other tools will not.

--

___
Python tracker 

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