[issue30434] multiprocessing AuthenticationError "digest sent was rejected"

[Xiang Zhang]

Xiang Zhang  added the comment:

I can't reproduce the failure with 2.7.13 but I do encounter the same failure 
just now, much same as yours, 2.7.5 and 2.7.13.  I'd like to describe my 
situation.

I have one client process started by 2.7.13(I build it from source) and one 
server process started by the system Python 2.7.5.  I then get the same error 
as yours, failing at connect() and the authkey doesn't matter.

The reason I find is that the system Python is patched by the OS vendor, 
changing the default MD5 algorithm to SHA256.  So they can't communicate.  
Patching the source or syncing the version works for me.

--
components: +Library (Lib)
nosy: +xiang.zhang
stage:  -> test needed

___
Python tracker 

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

[issue25942] subprocess.call SIGKILLs too liberally

[Martin Panter]

Martin Panter  added the comment:

https://github.com/python/cpython/pull/4283 adds a secondary timeout, which 
defaults to 1 s when there is no main timeout. But this seems complicated and 
arbitrary. As I understand, the main use case discussed here was waiting 
without a timeout for a child that exits soon after the interrupt. But are 
there any practical use cases or demand for:

* Limiting the wait time after the interrupt (despite no timeout before the 
interrupt)?
* Customizing this additional timeout?

--

___
Python tracker 

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

[issue29710] Incorrect representation caveat on bitwise operation docs

[Nick Coghlan]

Nick Coghlan  added the comment:

Right, and that's why I think we're better off focusing on the arithmetic 
explanations wherever they apply. The problem is that for "x | y" and "x & y" 
there's no avoiding discussing the 2's complement representation.

Martin, would you find the reference to `bit_length()` in the current PR easier 
to follow if it had a second follow-up sentence like the one below:

===
Bitwise binary operations are semantically equivalent to calculations
using 2's complement in a bit-width of ``1 + max(x.bit_length(), y
.bit_length()``. This choice of bit-width ensures there is sufficient space for 
the absolute value of both operands, while also providing space for an explicit 
sign bit (representing the conceptually infinite series of zeros or ones at the 
left of a 2's complement value).
===

That retains the precision of the currently suggested definition (for the 
benefit of language implementors), but also spells out the rationale for that 
definition (the "1 +" is for the sign bit, while the abs() is implicit in the 
fact that bit_length() assumes 2's complement and hence doesn't allow space for 
an explicit sign bit).

--

___
Python tracker 

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

[issue31953] Dedicated place for security announcements?

[Mariatta Wijaya]

Mariatta Wijaya  added the comment:

There is Security SIG mailing list, please check it out:
https://mail.python.org/mm3/archives/list/security-...@python.org/

--
nosy: +Mariatta
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

[issue29710] Incorrect representation caveat on bitwise operation docs

[Martin Panter]

Martin Panter  added the comment:

I find the model in terms of “bit_length” hard to understand. You have to 
understand what bit_length returns, and why you added 1. Bit_length is awkward 
for negative numbers. It only uses the absolute value, which would give 
off-by-one problems with negative values, so I guess you added 1 to compensate.

I understand the bitwise operations as using two’s complement extended to an 
unlimited width, so that negative values have a series of ones for the 
most-significant bits. I presume this is what your “2-adic representation” is. 
Having this spelled out may have helped when I was learning Python.

--
nosy: +martin.panter

___
Python tracker 

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

[issue31952] Weird behavior on tupple item assignment

[Emanuel Barry]

Emanuel Barry  added the comment:

This is a known issue, and is properly explained here: 
https://docs.python.org/3/faq/programming.html#why-does-a-tuple-i-item-raise-an-exception-when-the-addition-works

--
nosy: +ebarry
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

[issue31952] Weird behavior on tupple item assignment

[Lucas Bertoldo]

Change by Lucas Bertoldo :


--
versions: +Python 2.7, Python 3.5

___
Python tracker 

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

[issue31953] Dedicated place for security announcements?

[Jean-Philippe Ouellet]

New submission from Jean-Philippe Ouellet :

Hello,

My apologies if this is not the right place to discus this.

I would like to ensure that I stay informed of any potential future security 
issues in python (specifically at least the cpython runtime and standard 
library, although select very-popular 3rd party libraries wouldn't hurt). I 
cannot find a single place where such announcements are guaranteed to land.

Good examples of the type of thing I am looking for are the openssl-announce 
list [1][2] and the golang-announce list [3], where the projects pre-announce 
"Hey, we're going to have a release on  which addresses a  security issue in ." and then announces again 
when patches are available such that responsible maintainers (such as I am 
trying to be) can ensure that updates are available to our users ASAP.

The python-announce-list [4] does not serve this purpose because it has lots of 
noise from initial release announcements about random 3rd party stuff, and the 
"security news" page [5] is really just a "how to disclose vulns" page.

Note that I'm *not* advocating for the creation of a pre-disclosure list! 
Python is such a ubiquitous piece of software that I don't think it's 
reasonable to expect that such a list could contain all affected parties 
without also leaking details to those who would cause harm. I'm only asking for 
something public that I can subscribe to in order to be sure I'll have a heads 
up of when patching is imminently required.

Regards,
Jean-Philippe
(a contributor to the Qubes OS project [6] whose security relies mostly on 
Python's and Xen's - and is on Xen's pre-disclosure list)

[1]: https://mta.openssl.org/pipermail/openssl-announce/2017-October/thread.html
[2]: 
https://mta.openssl.org/pipermail/openssl-announce/2017-November/thread.html
[3]: https://groups.google.com/forum/#!forum/golang-announce
[4]: https://mail.python.org/mailman/listinfo/python-announce-list
[5]: https://www.python.org/news/security/
[6]: https://www.qubes-os.org/

--
assignee: docs@python
components: Documentation, email
messages: 305614
nosy: barry, docs@python, jpo, r.david.murray
priority: normal
severity: normal
status: open
title: Dedicated place for security announcements?
type: security

___
Python tracker 

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

[issue31952] Weird behavior on tupple item assignment

[Lucas Bertoldo]

New submission from Lucas Bertoldo :

Basically, I typed:
>>> m = (list(), list())

then I got, this, as expected:
>>> m[0] += [1]
Traceback (most recent call last):
  File "", line 1, in 
m[0] += [1]
TypeError: 'tuple' object does not support item assignment

but, when I checked the variable...
>>> m
([1], [])

-
Saying the least, one can kind of assing a value to a tuple of lists and get 
the expected result, but with the trackback still showing up.

--
components: Interpreter Core
files: python bug.png
messages: 305613
nosy: Lucas Bertoldo
priority: normal
severity: normal
status: open
title: Weird behavior on tupple item assignment
type: behavior
versions: Python 3.6
Added file: https://bugs.python.org/file47252/python bug.png

___
Python tracker 

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

[issue21790] Change blocksize in http.client to the value of resource.getpagesize

[Martin Panter]

Martin Panter  added the comment:

Issue 31945 proposes adding a “blocksize” parameter to HTTPConnection objects, 
so I suggest to closing in favour of that one.

--
resolution:  -> rejected
superseder:  -> Configurable blocksize in HTTP(S)Connection

___
Python tracker 

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

[issue28716] Fractions instantiation revisited

[Eric Wieser]

Eric Wieser  added the comment:

> allows Fraction instantiation from duck-typing classes that provide 
> as_integer_ratio

This would allow the numpy `np.floating` types to take part in `Fraction` 
conversion as well, which would be great.

As far as I can tell, `Decimal` already follows this duck-typing, so it would 
be a shame for other modules not to.

Perhaps an `num, den = operator.rational(x)` is needed to unify this code 
across the places that coerce rational numbers.

--
nosy: +Eric.Wieser

___
Python tracker 

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

[issue31951] import curses is broken on windows

[joe m]

New submission from joe m :

Importing curses on Windows install calls the following:

Traceback (most recent call last):
  File "", line 1, in 
  File "C:\Users\user 
name\AppData\Local\Programs\Python\Python36-32\lib\curses\__init__.py", line 
13, in 
from _curses import *
ModuleNotFoundError: No module named '_curses'

Importing curses as "_curses" does the same thing. I have tried the "repair" 
function and it has not worked.

--
components: Windows
messages: 305610
nosy: joe m2, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: import curses is broken on windows
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

[issue28140] Attempt to give better errors for pip commands typed into the REPL

[Tom Viner]

Change by Tom Viner :


--
nosy: +tomviner

___
Python tracker 

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

[issue30699] Misleading class names in datetime.tzinfo usage examples

[Mario Corchero]

Change by Mario Corchero :


--
nosy: +mariocj89

___
Python tracker 

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

[issue30699] Misleading class names in datetime.tzinfo usage examples

[Mario Corchero]

Change by Mario Corchero :


--
keywords: +patch
pull_requests: +4253
stage:  -> patch review

___
Python tracker 

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

[issue30548] typo in documentation for create_autospec

[Mario Corchero]

Mario Corchero  added the comment:

I've always understood instance as a way to say "I am passing this class but I 
want to force the autospec on the instance"

For example, given

```
class X:
def __init__(self):
raise
```

You can do `unittest.mock.create_autospec(X, instance=True)` to set a spec of 
the instance rather than the class.

Also quite often you do autospec on a class but you want the interface of the 
instance. This parameter allows you to do so.

Basically, `unittest.mock.create_autospec(X, instance=True)` will produce a non 
callable mock.

I think the docs are correct, maybe misleading

--
nosy: +mariocj89

___
Python tracker 

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

[issue31939] Support return annotation in signature for Argument Clinic

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

Victor is talking about inspect.signature(). In Python 3.5+ the result is "(fd, 
/)". In older versions it raises a ValueError. The docstring in 3.4 is 'dup(fd) 
-> fd2\n\nReturn a duplicate of a file descriptor.' It doesn't contain 
information that dup() returns int. It contains implicit information that dup() 
perhaps returns other file descriptor, but this is already explicitly 
documented by words. I don't see a loss of information here.

--

___
Python tracker 

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

[issue31950] Default event loop policy doc lacks precision

[Antoine Pitrou]

New submission from Antoine Pitrou :

The doc for the default event loop policy states that """the default policy 
defines context as the current thread, and manages an event loop per thread 
that interacts with asyncio""".  What it doesn't mention, though, is that you 
get a RuntimeError if you call get_event_loop() in a non-main thread -- you 
first have to call set_event_loop(new_event_loop()) in that thread.  This 
wasn't expected by me.

As a side note, customizing the event loop policy isn't trivial either: it 
seems it's best to subclass DefaultEventLoopPolicy and make adjustments by 
overriding the API methods.  Writing your own wouldn't work, as e.g. the Unix 
default policy has custom initialization code for child watchers.

--
assignee: docs@python
components: Documentation, asyncio
messages: 305607
nosy: docs@python, giampaolo.rodola, gvanrossum, haypo, pitrou, yselivanov
priority: normal
severity: normal
status: open
title: Default event loop policy doc lacks precision
type: behavior
versions: Python 3.6, Python 3.7

___
Python tracker 

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

[issue31939] Support return annotation in signature for Argument Clinic

[Brett Cannon]

Brett Cannon  added the comment:

R. David is correct that currently the policy is there are no type hints in the 
stdlib. Now the interesting thing about AC is the type hint info could be kept 
just in the docstring and not added to __annotations__ which somewhat goes 
around this restriction. Plus I think Victor is only talking about the 
docstring ATM anyway.

--

___
Python tracker 

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

[issue21423] concurrent.futures.ThreadPoolExecutor/ProcessPoolExecutor should accept an initializer argument

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Unfortunately, there is no obvious way to capture the output of the child 
process here, short of running the entire test under a subprocess.

--

___
Python tracker 

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

[issue31863] Inconsistent returncode/exitcode for terminated child processes on Windows

[Paul Moore]

Paul Moore  added the comment:

I'm not actually sure what the proposal here is. Are we suggesting that all 
Python's means of terminating a process should use the same exit code?

Note that doing so would be a backward compatibility break, as os.kill() is 
documented as having the behaviour seen here (it's just that SIGTERM isn't a 
particularly meaningful value to use on Windows). subprocess terminate() 
doesn't document the exit code sent on Windows, and maybe should - but 1 seems 
a reasonable value (it's the C EXIT_FAILURE code after all). I don't fully 
understand the issue multiprocessing is trying to solve, but it seems to be 
around signals, which are very different between Windows and Unix anyway.

So, in summary - I'd need to see a specific proposal, but my instinct is that 
this is only an issue if you're trying to cover over the differences between 
Unix and Windows, and this isn't a case where I think that's advisable (the 
current situation is "good enough" if you don't care, and if you do, you have 
the means to do it right, you just need to cater for the platform differences 
yourself, in a way that suits your application.).

--

___
Python tracker 

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

[issue31415] Add -X option to show import time

[Barry A. Warsaw]

Barry A. Warsaw  added the comment:

On Nov 4, 2017, at 14:29, Terry J. Reedy  wrote:

> The importtime output is sent to stderr.  Should this be documented?

Yes. :)

--

___
Python tracker 

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

[issue21423] concurrent.futures.ThreadPoolExecutor/ProcessPoolExecutor should accept an initializer argument

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

And please don't forget to edit a commit message when merge a PR.

--

___
Python tracker 

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

[issue21423] concurrent.futures.ThreadPoolExecutor/ProcessPoolExecutor should accept an initializer argument

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

test_concurrent_futures now produces too much output on stderr.

$ ./python -m test test_concurrent_futures >/dev/null
Exception in initializer:
Traceback (most recent call last):
  File "/home/serhiy/py/cpython/Lib/concurrent/futures/process.py", line 170, 
in _process_worker
initializer(*initargs)
  File "/home/serhiy/py/cpython/Lib/test/test_concurrent_futures.py", line 66, 
in init_fail
raise ValueError('error in initializer')
ValueError: error in initializer
Exception in initializer:
Traceback (most recent call last):
  File "/home/serhiy/py/cpython/Lib/concurrent/futures/process.py", line 170, 
in _process_worker
initializer(*initargs)
  File "/home/serhiy/py/cpython/Lib/test/test_concurrent_futures.py", line 66, 
in init_fail
raise ValueError('error in initializer')
ValueError: error in initializer
...

What is worse, this output looks as errors report.

--
nosy: +serhiy.storchaka
resolution: fixed -> 
stage: resolved -> 
status: closed -> open

___
Python tracker 

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

[issue31939] Support return annotation in signature for Argument Clinic

[R. David Murray]

R. David Murray  added the comment:

I believe we currently have a policy that the python standard library will not 
include type annotations, that those are provided by typeshed.

--
nosy: +r.david.murray

___
Python tracker 

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

[issue27359] OrderedDict pseudo-literals (WIP)

[Stefan Krah]

Stefan Krah  added the comment:

It looks like guaranteed ordered literals are going to happen (yay!):

   https://mail.python.org/pipermail/python-dev/2017-November/150144.html

--
nosy: +skrah
resolution: later -> out of date
stage:  -> resolved
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

[issue31863] Inconsistent returncode/exitcode for terminated child processes on Windows

[Antoine Pitrou]

Antoine Pitrou  added the comment:

I would like to know what our resident Windows users think about this (Paul, 
Steve, Zach).

Reading the above arguments, I'd be inclined to settle on 15 (that is, the 
non-negative "signal" number).  While it is not consistent with what "taskkill" 
or other APIs do, it makes it clear that the process was terminated in a 
certain way.  Certainly, there is a slight chance that 15 is a legitimate error 
code returned by the process, but that is far less likely than returning 1 as a 
legitimate error code, which I presume is extremely common.

In any case, this can't go in a bugfix release, so marking as 3.7-only.

--
versions:  -Python 3.6, Python 3.8

___
Python tracker 

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

[issue12276] 3.x ignores sys.tracebacklimit=0

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

Do you mind to create a pull request on GitHub Anand?

Issue31949 fixes this and several other bugs in PyTraceBack_Print(), but it may 
be worth to fix this bug first, especially if the patch contains tests.

--
assignee: docs@python -> serhiy.storchaka
components:  -Documentation
nosy: +serhiy.storchaka
versions: +Python 3.7 -Python 3.5

___
Python tracker 

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

[issue31949] Bugs in PyTraceBack_Print()

[Berker Peksag]

Berker Peksag  added the comment:

> Setting sys.tracebacklimit to 0 or less no longer suppress printing
> tracebacks in PyTraceBack_Print().

This was also reported in issue 12276.

--
nosy: +berker.peksag

___
Python tracker 

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

[issue31949] Bugs in PyTraceBack_Print()

[Serhiy Storchaka]

Change by Serhiy Storchaka :


--
keywords: +patch
pull_requests: +4252
stage:  -> patch review

___
Python tracker 

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

[issue31949] Bugs in PyTraceBack_Print()

[Serhiy Storchaka]

New submission from Serhiy Storchaka :

0fbab7ff8d2efd92e222fcc13c0aff0998c3c158 changed the semantic of 
PyTraceBack_Print and sys.tracebacklimit. It no longer match the documentation 
and the behavior of the traceback module. Setting sys.tracebacklimit to 0 or 
less no longer suppress printing tracebacks in PyTraceBack_Print(). Setting 
sys.tracebacklimit to None (as at shutdown stage) no longer makes 
PyTraceBack_Print() using default limit, but suppress printing tracebacks and 
sets a TypeError without returning failure from PyTraceBack_Print().

The proposed PR restores the initial purposed semantic and fixes several other 
bugs in PyTraceBack_Print().

* Setting sys.tracebacklimit to 0 or less now suppress printing tracebacks.
* Setting sys.tracebacklimit to None now causes using the default limit.
* Setting sys.tracebacklimit to an integer larger than LONG_MAX now means using 
the limit LONG_MAX rather than the default limit.
* Fixed integer overflows in the case of more than 2**31 items on Windows.
* Fixed output errors handling.

--
assignee: serhiy.storchaka
components: Interpreter Core
messages: 305595
nosy: christian.heimes, serhiy.storchaka
priority: normal
severity: normal
status: open
title: Bugs in PyTraceBack_Print()
type: behavior
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

[issue31454] Include "import as" in tutorial

[Berker Peksag]

Berker Peksag  added the comment:

PR 4041 looks good to me. Mariatta, do you have time to look at Mario's patch?

Sarthak, thank you for your PR, but a PR was opened 12 days before yours 
(sorry, I missed it earlier) Would you like to work on another issue? I've just 
opened bpo-31948 and I'd be happy to review/merge a PR if you have time. Thanks!

--

___
Python tracker 

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

[issue31948] Broken MSDN links in msilib docs

[Berker Peksag]

New submission from Berker Peksag :

Most of the MSDN links in Doc/library/msilib.rst are broken:

   https://docs.python.org/3/library/msilib.html

For example, the UuidToString link goes to

   
https://msdn.microsoft.com/library?url=/library/en-us/rpc/rpc/uuidtostring.asp

But I believe the correct link should be


https://msdn.microsoft.com/en-us/library/windows/desktop/aa379352(v=vs.85).aspx

--
assignee: docs@python
components: Documentation
keywords: easy
messages: 305593
nosy: berker.peksag, docs@python
priority: normal
severity: normal
stage: needs patch
status: open
title: Broken MSDN links in msilib docs
type: behavior
versions: Python 3.6, Python 3.7

___
Python tracker 

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

[issue31939] Support return annotation in signature for Argument Clinic

[Tal Einat]

Tal Einat  added the comment:

Argument Clinic currently doesn't support input parameter type annotations 
either, though for this it has more relevant information in many cases.

I think it would be a great boon for AC to enable declaring type annotations, 
both for input parameters and for return values.

--

___
Python tracker 

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

[issue31947] names=None case is not handled by EnumMeta._create_ method

[Paul]

New submission from Paul :

It seems to me that this method should not have names=None default value in 
signature, because that case is not handled, nor is it described as a possible 
value in the docstring.

Seems like maybe a copy and paste from __call__, which has basically same 
signature, but names=None is valid and handled there.

--
messages: 305591
nosy: anentropic
priority: normal
pull_requests: 4251
severity: normal
status: open
title: names=None case is not handled by EnumMeta._create_ method
type: behavior
versions: Python 3.4, Python 3.5, 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

[issue31921] Bring together logic for entering/leaving a frame in frameobject.c

[pdox]

Change by pdox :


--
resolution:  -> rejected

___
Python tracker 

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

[issue31921] Bring together logic for entering/leaving a frame in frameobject.c

[pdox]

pdox  added the comment:

Raymond, this is not an experiment, but the beginning of a sustained effort to 
improve locality during execution, to make more effective use of CPU cache 
lines. Rather than discuss the details of this change one PR at a time, I will 
close this issue for now, and open a discussion on python-dev.

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

[issue11063] Rework uuid module: lazy initialization and add a new C extension

[Stefan Krah]

Stefan Krah  added the comment:

Berker's latest patch looks good to me.

Unrelated to the patch (same before and after), this looks odd to me:

>>> import uuid
>>> uuid._has_uuid_generate_time_safe is None
True
>>> 
>>> import _uuid
>>> _uuid.has_uuid_generate_time_safe
1


[Also, I thought we weren't supposed to use ctypes in the stdlib.]

--

___
Python tracker 

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

[issue28994] Misc fixes and cleanups in error handling C code

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:


New changeset cf296537f164abeacd83011239881f75f290ed31 by Serhiy Storchaka in 
branch 'master':
bpo-28994: PyErr_NormalizeException() no longer use C stack for recursion. 
(#2035)
https://github.com/python/cpython/commit/cf296537f164abeacd83011239881f75f290ed31


--

___
Python tracker 

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

[issue11063] Rework uuid module: lazy initialization and add a new C extension

[Berker Peksag]

Berker Peksag  added the comment:

I've followed Stefan's suggestion and opened PR 4287 (tested on 10.10.5)

--
nosy: +berker.peksag

___
Python tracker 

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

[issue11063] Rework uuid module: lazy initialization and add a new C extension

[Berker Peksag]

Change by Berker Peksag :


--
pull_requests: +4250

___
Python tracker 

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