[issue33162] TimedRotatingFileHandler in logging module

Change by Nitish : -- nosy: +nitishch ___ Python tracker ___ ___ Python-bugs-list

[issue33204] IDLE: remove \b from colorizer string prefix

Change by miss-islington : -- pull_requests: +6056 ___ Python tracker ___

[issue33204] IDLE: remove \b from colorizer string prefix

Change by miss-islington : -- pull_requests: +6055 ___ Python tracker ___

[issue33204] IDLE: remove \b from colorizer string prefix

Terry J. Reedy added the comment: New changeset da58533ac67b01ce8f6466e6f03ff6b8b3bb04d5 by Terry Jan Reedy in branch 'master': bpo-33204: IDLE: consistently color invalid string prefixes (#6344)

[issue27212] Doc for itertools, 'islice()' implementation have unwanted behavior for recipe 'consume()'

Raymond Hettinger added the comment: Thanks Cheryl. This was nice work :-) -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue27212] Doc for itertools, 'islice()' implementation have unwanted behavior for recipe 'consume()'

Raymond Hettinger added the comment: New changeset 325191bd6b3a2d5e3012adee868f19baf3e2c3ab by Raymond Hettinger (Cheryl Sabella) in branch '2.7': [2.7] bpo-27212: Modify islice recipe to consume initial values preceding start (GH-6195) (GH-6339)

[issue33197] Confusing error message when constructing invalid inspect.Parameters

Nitish added the comment: Also, _ParameterKind class has a __str__ method. So, I guess it's better to use "{!s}" in the format string instead of using kind.name. -- ___ Python tracker

[issue33197] Confusing error message when constructing invalid inspect.Parameters

Nitish added the comment: @Antony Lee since you know the fix, do you want to submit a PR? -- nosy: +nitishch ___ Python tracker

[issue33204] IDLE: remove \b from colorizer string prefix

Change by Terry J. Reedy : -- stage: test needed -> patch review ___ Python tracker ___

[issue33204] IDLE: remove \b from colorizer string prefix

Terry J. Reedy added the comment: To see the visually verified test, run Lib/idlelib/colorizer as the main module, either from a command line or editor, and click the button. -- stage: patch review -> test needed ___ Python

[issue33204] IDLE: remove \b from colorizer string prefix

Change by Terry J. Reedy : -- keywords: +patch pull_requests: +6054 stage: test needed -> patch review ___ Python tracker ___

[issue33204] IDLE: remove \b from colorizer string prefix

Tim Peters added the comment: Sounds good (removing \b) to me, Terry! -- nosy: +tim.peters ___ Python tracker ___

Re: Why is the use of an undefined name not a syntax error?

On 4/1/2018 5:24 PM, David Foster wrote: My understanding is that the Python interpreter already has enough information when bytecode-compiling a .py file to determine which names correspond to local variables in functions. That suggests it has enough information to identify all valid names

Re: How to fill in a dictionary with key and value from a string?

On 02/04/18 03:24, C W wrote: Thank you Steven. I am frustrated that I can't enumerate a dictionary by position index. Maybe I want to shift by 2 positions, 5 positions... I want to know/learn how to manipulate dictionary with loop and by its position location. Frankly I think you'd be much

[issue33012] Invalid function cast warnings with gcc 8 for METH_NOARGS

Martin Panter added the comment: Siddhesh, it looks like your fixes make the C function signatures match the signature expected in the PyMethodDef structure. If so, I suggest to remove the (PyCFunction) casts from those structure definitions as well. For instance, now

Re: How to fill in a dictionary with key and value from a string?

Yes, you see right through me! I was able to conquer it, there's probably better ways: self.myDict = dict(zip(string.ascii_lowercase + string.ascii_uppercase, string.ascii_lowercase[shift:26] + string.ascii_lowercase[:shift] + string.ascii_uppercase[shift:26] + string.ascii_uppercase[:shift]))

[issue33204] IDLE: remove \b from colorizer string prefix

Terry J. Reedy added the comment: The current test is part of the htest. The section # All valid prefixes for unicode and byte strings should be colored contains "ur'is invalid'". This should be moved to a new section with other invalid combinations. # Invalid combinations

[issue33204] IDLE: remove \b from colorizer string prefix

New submission from Terry J. Reedy : Lib\idlelib\colorizer.py, line 25, is: stringprefix = r"(?i:\br|u|f|fr|rf|b|br|rb)?" The r prefix, but only the r prefix, must be preceded by a non-word character. On pydev thread "IDLE colorizer", MRAB noted: "The \b will apply only to

Re: How to fill in a dictionary with key and value from a string?

On Sun, 01 Apr 2018 22:24:31 -0400, C W wrote: > Thank you Steven. I am frustrated that I can't enumerate a dictionary by > position index. Why do you care about position index? > Maybe I want to shift by 2 positions, 5 positions... Sounds like you are trying to program the Caesar Shift

Re: How to fill in a dictionary with key and value from a string?

Thank you Steven. I am frustrated that I can't enumerate a dictionary by position index. Maybe I want to shift by 2 positions, 5 positions... I want to know/learn how to manipulate dictionary with loop and by its position location. On Sun, Apr 1, 2018 at 10:02 PM, Steven D'Aprano <

Re: How to fill in a dictionary with key and value from a string?

On Sun, 01 Apr 2018 20:52:35 -0400, C W wrote: > Thank you all for the response. > > What if I have myDict = {'a': 'B', 'b': 'C',...,'z':'A' }? So now, the > values are shift by one position. > > key:abcdefghijklmnopqrstuvwxyz > value: BCDEFGHIJKLMNOPQRSTUVWXYZA > > Can I fill in a key and

Re: Why is the use of an undefined name not a syntax error?

On Sun, 01 Apr 2018 14:24:38 -0700, David Foster wrote: > My understanding is that the Python interpreter already has enough > information when bytecode-compiling a .py file to determine which names > correspond to local variables in functions. That suggests it has enough > information to

Re: How to fill in a dictionary with key and value from a string?

I am using Python 3.6. I ran the those lines and got a sorted dictionary by keys. On Sun, Apr 1, 2018 at 9:38 PM, Chris Angelico wrote: > On Mon, Apr 2, 2018 at 11:34 AM, C W wrote: > > A different but related question: > > > > myDict =

Re: How to fill in a dictionary with key and value from a string?

On Mon, Apr 2, 2018 at 11:34 AM, C W wrote: > A different but related question: > > myDict = dict(zip(string.ascii_lowercase + string.ascii_uppercase, > string.ascii_lowercase + string.ascii_uppercase)) >>myDict > {'A': 'A', 'B': 'B', 'C': 'C',...,'w': 'w', 'x': 'x', 'y': 'y',

Re: How to fill in a dictionary with key and value from a string?

A different but related question: myDict = dict(zip(string.ascii_lowercase + string.ascii_uppercase, string.ascii_lowercase + string.ascii_uppercase)) >myDict {'A': 'A', 'B': 'B', 'C': 'C',...,'w': 'w', 'x': 'x', 'y': 'y', 'z': 'z'} Why are the keys sorted from upper case to lower case? I asked

Re: check if bytes is all nulls

On Sun, 01 Apr 2018 19:14:05 +, Arkadiusz Bulski wrote: > Thanks, > timeit gives `not any(key)` same performance as `sum(key)==0`. Have you considered what happens when the key is *not* all zeroes? key = b'\x11'*100 any(key) bails out on the first byte. sum(key) has to add a million

[issue30940] Documentation for round() is incorrect.

Change by Lisa Roach : -- keywords: +patch pull_requests: +6053 ___ Python tracker ___

Re: How to fill in a dictionary with key and value from a string?

Thank you all for the response. What if I have myDict = {'a': 'B', 'b': 'C',...,'z':'A' }? So now, the values are shift by one position. key:abcdefghijklmnopqrstuvwxyz value: BCDEFGHIJKLMNOPQRSTUVWXYZA Can I fill in a key and its corresponding value simultaneously on the fly? Something in

[issue33199] PyDict_Copy() can leave 'ma_version_tag' uninitialized

Change by INADA Naoki : -- keywords: +patch pull_requests: +6052 stage: -> patch review ___ Python tracker ___

[issue33199] PyDict_Copy() can leave 'ma_version_tag' uninitialized

Change by INADA Naoki : -- versions: -Python 3.4, Python 3.5 ___ Python tracker ___

[issue33196] SEGV in mp.synchronize.Lock.__repr__ in spawn'ed proc if ctx mismatched

Antoine Pitrou added the comment: Thanks for the report. Indeed I think it would be worth preventing this programmer error. -- nosy: +pitrou stage: -> needs patch versions: +Python 3.7, Python 3.8 ___ Python tracker

[issue15088] PyGen_NeedsFinalizing is public, but undocumented

Antoine Pitrou added the comment: Cheryl: it may be useful to do a code search to find out whether any third-party projects are relying on PyGen_NeedsFinalizing. -- ___ Python tracker

[issue33192] asyncio should use signal.set_wakeup_fd on Windows

Change by Antoine Pitrou : -- components: +Library (Lib) stage: -> needs patch type: -> behavior ___ Python tracker ___

Re: Why is the use of an undefined name not a syntax error?

David Foster writes: > My understanding is that the Python interpreter already has enough > information when bytecode-compiling a .py file to determine which > names correspond to local variables in functions. That suggests it has > enough information to identify all valid

[issue33200] Optimize the empty set "literal"

Antoine Pitrou added the comment: > Does anyone seriously write "{*()}" instead of "set()"? It doesn't seem to be laughing to me. -- nosy: +pitrou ___ Python tracker

[issue27212] Doc for itertools, 'islice()' implementation have unwanted behavior for recipe 'consume()'

Change by Cheryl Sabella : -- pull_requests: +6051 ___ Python tracker ___ ___

[issue22781] ctypes: Differing results between Python and C.

Martin Panter added the comment: Eryk Sun’s explanation makes this sound like a duplicate of Issue 15453, which shows GCC on Linux packing structures into a single byte, and ctypes using the size of the expanded integer type. -- nosy: +martin.panter resolution:

Re: Why is the use of an undefined name not a syntax error?

On Mon, Apr 2, 2018 at 8:05 AM, Devin Jeanpierre wrote: > On Sun, Apr 1, 2018 at 2:38 PM, Chris Angelico wrote: >> On Mon, Apr 2, 2018 at 7:24 AM, David Foster wrote: >>> My understanding is that the Python interpreter already has

Re: Why is the use of an undefined name not a syntax error?

On Sun, Apr 1, 2018 at 2:38 PM, Chris Angelico wrote: > On Mon, Apr 2, 2018 at 7:24 AM, David Foster wrote: >> My understanding is that the Python interpreter already has enough >> information when bytecode-compiling a .py file to determine which names >>

[issue33199] PyDict_Copy() can leave 'ma_version_tag' uninitialized

Change by Antoine Pitrou : -- nosy: +inada.naoki, rhettinger ___ Python tracker ___ ___

Re: Why is the use of an undefined name not a syntax error?

> But if it is cheap to detect a wide variety of name errors at compile time, > is there any particular reason it is not done? >From my perspective, it is done, but by tools that give better output than Python's parser. :) Linters (like pylint) are better than syntax errors here, because they

Re: Why is the use of an undefined name not a syntax error?

On Mon, Apr 2, 2018 at 7:24 AM, David Foster wrote: > My understanding is that the Python interpreter already has enough > information when bytecode-compiling a .py file to determine which names > correspond to local variables in functions. That suggests it has enough >

Why is the use of an undefined name not a syntax error?

My understanding is that the Python interpreter already has enough information when bytecode-compiling a .py file to determine which names correspond to local variables in functions. That suggests it has enough information to identify all valid names in a .py file and in particular to identify

[issue33144] random._randbelow optimization

Wolfgang Maier added the comment: ok, I've created issue 33203 to deal with raising ValueError in _randbelow consistently. -- ___ Python tracker

[issue33203] random.choice: raise IndexError on empty sequence even when not using getrandbits internally

Change by Wolfgang Maier : -- keywords: +patch pull_requests: +6050 stage: -> patch review ___ Python tracker

[issue33203] random.choice: raise IndexError on empty sequence even when not using getrandbits internally

New submission from Wolfgang Maier : from https://docs.python.org/3/library/random.html#random.choice: Return a random element from the non-empty sequence seq. If seq is empty, raises IndexError. Indeed: >>> import random >>> random.choice([])

[issue33202] os.walk mentions os.listdir instead of os.scandir

New submission from Andrés Delfino : Documentation states that, for walk, "errors from the listdir() call are ignored". That's no longer the case since 3.5. Change mention to listdir() to scandir(). -- assignee: docs@python components: Documentation messages:

Re: check if bytes is all nulls

Arkadiusz Bulski wrote: > Thanks, > timeit gives `not any(key)` same performance as `sum(key)==0`. Then you did not feed it the "right" data $ python3 -m timeit -s 'key = b"x" + bytes(10**6)' 'sum(key)' 100 loops, best of 3: 15.7 msec per loop $ python3 -m timeit -s 'key = b"x" + bytes(10**6)'

Re: check if bytes is all nulls

On Mon, Apr 2, 2018 at 5:14 AM, Arkadiusz Bulski wrote: > Thanks, > timeit gives `not any(key)` same performance as `sum(key)==0`. Are you timing these on ten-byte keys, or really large keys? For short keys, just use whatever looks most elegant, and don't worry about

[issue33191] Refleak in posix_spawn

Gregory P. Smith added the comment: https://github.com/python/cpython/pull/6332 appears to address this. -- ___ Python tracker ___

Re: check if bytes is all nulls

2018-04-01 22:03 GMT+03:00 Kirill Balunov : > > > 2018-04-01 20:55 GMT+03:00 Arkadiusz Bulski : > >> What would be the most performance efficient way of checking if a bytes is >> all zeros? > > > Try `not any(key)` ;) > > Sorry, I don't timed it

[issue33201] Modernize "Extension types" documentation

Change by Antoine Pitrou : -- keywords: +patch pull_requests: +6048 stage: needs patch -> patch review ___ Python tracker ___

Re: check if bytes is all nulls

Thanks, timeit gives `not any(key)` same performance as `sum(key)==0`. niedz., 1 kwi 2018 o 21:03 użytkownik Kirill Balunov < kirillbalu...@gmail.com> napisał: > 2018-04-01 20:55 GMT+03:00 Arkadiusz Bulski : > >> What would be the most performance efficient way of

[issue20104] expose posix_spawn(p)

miss-islington added the comment: New changeset ab8457232121dfdfb1d4bfcf806a842fbe402722 by Miss Islington (bot) in branch '3.7': bpo-20104: Add os.posix_spawn documentation. (GH-6334)

[issue20104] expose posix_spawn(p)

Gregory P. Smith added the comment: PR 6332 is overall a good cleanup. I pushed a couple changes to that PR and left comments for some others. It should go in. There are basic tests for os.posix_spawn in test_posix.py. More would be nice as we don't currently have any for

Re: check if bytes is all nulls

2018-04-01 20:55 GMT+03:00 Arkadiusz Bulski : > What would be the most performance efficient way of checking if a bytes is > all zeros? Try `not any(key)` ;) With kind regards, -gdg -- https://mail.python.org/mailman/listinfo/python-list

[issue33201] Modernize "Extension types" documentation

New submission from Antoine Pitrou : The "Defining New Types" in the C extension docs uses outdated idioms (e.g. pre-C99 struct initialization) and could do with a good refresh. -- assignee: docs@python components: Documentation messages: 314782 nosy: docs@python,

[issue20104] expose posix_spawn(p)

Gregory P. Smith added the comment: New changeset 79760ed256987cead08d668b95675afba6b3760f by Gregory P. Smith in branch 'master': bpo-20104: Add os.posix_spawn documentation. (#6334) https://github.com/python/cpython/commit/79760ed256987cead08d668b95675afba6b3760f

[issue20104] expose posix_spawn(p)

Change by miss-islington : -- pull_requests: +6047 ___ Python tracker ___

[issue20104] expose posix_spawn(p)

Change by Gregory P. Smith : -- pull_requests: +6046 ___ Python tracker ___ ___

Re: check if bytes is all nulls

On 01/04/2018 18:55, Arkadiusz Bulski wrote: What would be the most performance efficient way of checking if a bytes is all zeros? Currently its `key == b'\x00' * len(key)` however, because its Python 2/3 compatible: That doesn't too efficient, if you first have to construct a compatible

Re: check if bytes is all nulls

Arkadiusz Bulski wrote: > What would be the most performance efficient way of checking if a bytes is > all zeros? Currently its `key == b'\x00' * len(key)` however, because its > Python 2/3 compatible: > > sum(key) == 0 is invalid > key == bytes(len(key)) is invalid > > I already considered

Re: check if bytes is all nulls

On 2018-04-01 18:55, Arkadiusz Bulski wrote: What would be the most performance efficient way of checking if a bytes is all zeros? Currently its `key == b'\x00' * len(key)` however, because its Python 2/3 compatible: sum(key) == 0 is invalid key == bytes(len(key)) is invalid I already

Re: Beta release of pip version 10

On 2018-04-01 11:26, Paul Moore wrote: On 1 April 2018 at 04:15, Mikhail V wrote: MRAB writes: > UnicodeEncodeError: 'charmap' codec can't encode character > > when it meets a non-ascii char. > > e.g. tried this: > pip search pygame > a.txt > Well, _I_ didn't get an

Re: check if bytes is all nulls

Some interesting timeits: In [7]: timeit('sum(x)==0', 'x=bytes(10)') Out[7]: 0.30194770699927176 In [11]: timeit('x==bytes(10)', 'x=bytes(10)') Out[11]: 0.2181608650007547 In [12]: timeit('x==z*10', 'x=bytes(10); z=bytes(1)') Out[12]: 0.1092393600010837 In [13]: timeit('x==x2', 'x=bytes(10);

check if bytes is all nulls

What would be the most performance efficient way of checking if a bytes is all zeros? Currently its `key == b'\x00' * len(key)` however, because its Python 2/3 compatible: sum(key) == 0 is invalid key == bytes(len(key)) is invalid I already considered precomputing the rhs value. Length of key is

Re: How to fill in a dictionary with key and value from a string?

On Mon, Apr 2, 2018 at 3:03 AM, Rustom Mody wrote: > On Saturday, March 31, 2018 at 4:30:04 PM UTC+5:30, bartc wrote: >> On 30/03/2018 21:13, C W wrote: >> > Hello all, >> > >> > I want to create a dictionary. >> > >> > The keys are 26 lowercase letters. The values are 26

Re: How to fill in a dictionary with key and value from a string?

On Saturday, March 31, 2018 at 4:30:04 PM UTC+5:30, bartc wrote: > On 30/03/2018 21:13, C W wrote: > > Hello all, > > > > I want to create a dictionary. > > > > The keys are 26 lowercase letters. The values are 26 uppercase letters. > > > > The output should look like: > > {'a': 'A', 'b':

[issue33189] pygettext doesn't work with f-strings

Serhiy Storchaka added the comment: I agree that pygettext should not and can not support f-strings, but the error should be better. The problem is that an f-string expression is tokenized as literal strings, but eval() can't evaluate it out of context.

[issue20104] expose posix_spawn(p)

Serhiy Storchaka added the comment: PR 6332 fixes issues found by me in os.posix_spawn(). It is not completed yet, needed documentation and tests. And I have doubts about API. -- ___ Python tracker

[issue20104] expose posix_spawn(p)

Change by Serhiy Storchaka : -- pull_requests: +6045 stage: commit review -> patch review ___ Python tracker ___

[issue29753] Ctypes Packing Bitfields Incorrectly - Linux

Marc Le Roy added the comment: No solution found to solve this issue ? The anomaly is not a cross platform inconsistency, it is an inconsistency between the behaviours of GCC and ctypes, both under Linux or Cygwin, when defining packed structures : [Marc@I7-860

[issue20104] expose posix_spawn(p)

Pablo Galindo Salgado added the comment: Notice that some of the errors identified at the end of 5109 were already corrected by the other PRs in this issue. -- ___ Python tracker

[issue33189] pygettext doesn't work with f-strings

Stefan Behnel added the comment: Is there really a use case for this? I would normally expect place holders to get replaced *after* translation, i.e. in the translated text, not before. -- nosy: +scoder ___ Python tracker

[issue20104] expose posix_spawn(p)

Pablo Galindo Salgado added the comment: In PR6331 I am trying to address all issues identified by Serhiy. -- ___ Python tracker

[issue33191] Refleak in posix_spawn

Change by Pablo Galindo Salgado : -- pull_requests: +6044 ___ Python tracker ___ ___

[issue20104] expose posix_spawn(p)

Ned Deily added the comment: > perhaps it would be better to remove this undocumented feature from 3.7 We need to make a decision about this before the b4 cutoff in 4 weeks. But it would not be fair to ask people to put in the effort to try to fix things if there is not a

[issue33194] Path-file objects does not have method to delete itself if its a file

Marco Rougeth added the comment: Wow, I never saw unlink term related to removing files (obviously I'm not an old-school Unix greybeard). @nsj could you point me the thread you talked about? or help me find it? I looked in the archive in the last three months and couldn't

[issue33200] Optimize the empty set "literal"

Serhiy Storchaka added the comment: Don't know. :-) Consider this as a 1st April egg. -- ___ Python tracker ___

[issue33200] Optimize the empty set "literal"

Mark Dickinson added the comment: Does anyone seriously write "{*()}" instead of "set()"? -- nosy: +mark.dickinson ___ Python tracker

[issue20104] expose posix_spawn(p)

Serhiy Storchaka added the comment: I'm trying to fix issues with os.posix_spawn(), but there are so much of them, that perhaps it would be better to remove this undocumented feature from 3.7. -- ___ Python tracker

[issue33200] Optimize the empty set "literal"

Change by Serhiy Storchaka : -- keywords: +patch pull_requests: +6043 stage: -> patch review ___ Python tracker ___

Re: Beta release of pip version 10

On 1 April 2018 at 03:16, MRAB wrote: > On 2018-04-01 02:50, Mikhail V wrote: >> >> Steven D'Aprano writes: >> PS: was looking forward to PIP improvements on Windows, on 9.0.3 still some issues. E.g. trying to redirect output from 'pip search ... >

[issue33200] Optimize the empty set "literal"

New submission from Serhiy Storchaka : The following PR optimizes bytecode for the empty set "literal": {*()}. Currently it is compiled to LOAD_CONST 0 (()) BUILD_SET_UNPACK 1 It will optimized to BUILD_SET0 $

Re: Beta release of pip version 10

On 1 April 2018 at 04:15, Mikhail V wrote: > MRAB writes: > > >> > UnicodeEncodeError: 'charmap' codec can't encode character >> > >> > when it meets a non-ascii char. >> > >> > e.g. tried this: >> > pip search pygame > a.txt >> > >> Well, _I_ didn't get an error! >> >> One

[issue33199] PyDict_Copy() can leave 'ma_version_tag' uninitialized

New submission from pdox : PyDict_Copy leaves 'ma_version_tag' uninitialized when the dictionary being copied has a split table. -- components: Interpreter Core messages: 314768 nosy: pdox priority: normal severity: normal status: open title: PyDict_Copy() can leave

[issue33198] Build on Linux with --enable-optimizations fails

New submission from Florian Schulze : While the tests run there is a segfault: https://travis-ci.org/collective/buildout.python/jobs/360190312#L2529 Started with b2 and still happens in b3, b1 built fine. -- components: Build, Tests messages: 314767 nosy:

[issue32713] tarfile.itn breaks if n is a negative float

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

[issue33096] ttk.Treeview.insert() does not allow to insert item with "False" iid

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

[issue33132] Possible refcount issues in the compiler

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 2.7 ___ Python tracker

[issue33132] Possible refcount issues in the compiler

Serhiy Storchaka added the comment: New changeset 72f3e0887500e00867fa16ce5aaab12fae853b63 by Serhiy Storchaka in branch '2.7': [2.7] bpo-33132: Fix reference counting issues in the compiler. (GH-6209). (GH-6322)

[issue33195] PyArg_Parse* should deprecate 'u' and 'z' family.

Serhiy Storchaka added the comment: See also issue24009. We should get rid of using these units in the stdlib. I'm not sure about deprecating Py_BuildValue() units right now. They can be redefined in terms of wchar_t, and they are already implemented with

[issue33197] Confusing error message when constructing invalid inspect.Parameters

New submission from Antony Lee : Python 3.6.4 In [15]: inspect.Parameter("foo", kind=inspect.Parameter.VAR_KEYWORD, default=42) --- ValueErrorTraceback

[issue33130] functools.reduce signature/docstring discordance

Nick Coghlan added the comment: +1 for switching over to `iterable` in the reduce docstring. As a possible enhancement for 3.8+ only, it would be reasonable to start converting functools over to Argument Clinic in order to improve the introspection support. (Note that

Re: GPG signatures invisible in new PyPI (was: Re: new Python Package Index is now in beta at pypi.org)

Hi Sumana, > I've been trying to reach out to the Debian Python community via IRC, > personal connections, tickets, and mailing lists to ensure a smooth > transition; I see now that a post I tried to get onto the debian-python > list a few weeks ago did not get posted there, so I've re-sent it.