[issue2306] Update What's new in 3.0

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: Raising to deferred blocker. This will definitely block 3.0rc3. -- nosy: +barry priority: high -> deferred blocker ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.py

[issue2306] Update What's new in 3.0

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: deferred blocker -> release blocker ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.py

[issue4236] Crash when importing builtin module during interpreter shutdown

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: deferred blocker -> release blocker ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.py

[issue3799] Byte/string inconsistencies between different dbm modules

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: deferred blocker -> release blocker ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.py

[issue4236] Crash when importing builtin module during interpreter shutdown

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: After consultation with MvL and Crys_ on irc, we've agreed that this should be fixed someday but it's a pathological case that shouldn't hold up the release. I'm lowering to critical because I don't think i

[issue4306] email package with unicode subject/body

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: This example works though, and it also works in earlier Pythons. from email.header import Header def main(): # coding: utf8 ADDRESS = '[EMAIL PROTECTED]' from email.mime.text import MIMEText msg = MIMEText(

[issue4306] email package with unicode subject/body

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: I'm rejecting the patch because the old way of making this work still works in Python 3.0. Any larger changes to the API need to be made in the context of redesigning the email package to be byte/str aware. --

[issue4360] SystemError when method has both super() & closure

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: patch applied; r67299 -- status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.py

[issue4362] FileIO object in io module

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: I'm okay with the roundtrip not being supported. One thing I don't quite understand is in the third test, where you're using "w+" mode and testing f.buffer.mode and f.buffer.raw.mode is "r+"

[issue4362] FileIO object in io module

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: r67300 (with after the fact whitespace normalization of Lib/tests/test_io.py) -- status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.py

[issue4306] email package with unicode subject/body

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 20, 2008, at 5:07 PM, STINNER Victor wrote: > STINNER Victor <[EMAIL PROTECTED]> added the comment: > >> I'm rejecting the patch because the old way of makin

[issue4362] FileIO object in io module

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> <http://bugs

[issue4362] FileIO object in io module

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- status: closed -> open ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4362> ___ __

[issue3741] DISTUTILS_USE_SDK set causes msvc9compiler.py to raise an exception

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: deferred blocker -> release blocker ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.py

[issue3741] DISTUTILS_USE_SDK set causes msvc9compiler.py to raise an exception

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3741> ___ ___ Python-bugs-list mailing list

[issue3799] Byte/string inconsistencies between different dbm modules

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: deferred blocker -> release blocker ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.py

[issue4373] Reference leaks in Python 3.0rc3

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: deferred blocker -> release blocker ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.py

[issue2306] Update What's new in 3.0

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: deferred blocker -> release blocker ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.py

[issue4303] [2.5 regression] ctypes fails to build on arm-linux-gnu

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: Deferring until 3.0 final is out. -- nosy: +barry priority: release blocker -> deferred blocker ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.py

[issue2306] Update What's new in 3.0

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: Guido... ping? ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2306> ___ ___ Python

[issue4449] AssertionError in Doc/includes/mp_benchmarks.py

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: Jesse, please apply so we can close this issue. -- nosy: +barry ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue4385] Py_Object_HEAD_INIT in Py3k

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: I agree with MvL and MAL. We can't change Python, so this is a documentation issue. I'm lowering the priority so it doesn't block the release. -- nosy: +barry priority: releas

[issue1683] Thread local storage and PyGILState_* mucked up by os.fork()

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: Since this is a Python 2.5.3 issue, I'm lowering to deferred blocker until after 3.0 and 2.6.1 are released. ------ nosy: +barry priority: release blocker -> deferred blocker ___

[issue4387] binascii b2a functions accept strings (unicode) as data

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: Martin, the patch looks okay to me. I vote for applying it. -- nosy: +barry resolution: -> accepted ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.py

[issue4469] CVE-2008-5031 multiple integer overflows

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: Lowering priority since this is not a Python 3.0 or 2.6.1 issue. -- nosy: +barry priority: release blocker -> deferred blocker ___ Python tracker <[EMAIL PROTECTED]> <http

[issue4365] Add CRT version info in msvcrt module

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: Go for it Martin. -- resolution: -> accepted versions: +Python 2.6, Python 3.0 ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.py

[issue2306] Update What's new in 3.0

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: Guido, ETA? I think this will be one of the last things before we can tag the tree for release. ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue4449] AssertionError in Doc/includes/mp_benchmarks.py

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: Jesse, does this affect Python 3.0? If not, then I will lower the priority and release 2.6.1 without it (there's always 2.6.2 :). If so, then we need to know if 1) it's really a release blocker; 2) what the ETA on a fix i

[issue4486] Exception traceback is incorrect for strange exception handling

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: This looks like it only affects printing exceptions with implicit chaining when the exception propagates to the top level. (Maybe it also affects the traceback module?) In that case, I agree with Antoine. Let's fix

[issue4449] AssertionError in Doc/includes/mp_benchmarks.py

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: I don't much like the lock is True lock is False idioms much, but I don' thave a better suggestion, and it would be nice to fix this for the releases. -- resolution: -> accepted ___

[issue4449] AssertionError in Doc/includes/mp_benchmarks.py

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: I've changed my mind based on the API change. This should be discussed on the mailing list and deferred until 2.6.2 at least. -- resolution: accepted -> ___ Python tracker <

[issue4025] C99 comments in Python 2.6 break build on AIX 6.1

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: For 2.6.1, yes you can fix the comments if you can do it now :) ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue4303] [2.5 regression] ctypes fails to build on arm-linux-gnu

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: deferred blocker -> release blocker ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.py

[issue1683] Thread local storage and PyGILState_* mucked up by os.fork()

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: deferred blocker -> release blocker ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.py

[issue4469] CVE-2008-5031 multiple integer overflows

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: deferred blocker -> release blocker ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.py

[issue4519] .pyc files included in 2.6 and 3.0 release tarballs

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: I thought we had fixed that :( -- priority: -> release blocker ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.py

[issue4519] .pyc files included in 2.6 and 3.0 release tarballs

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: Actually, it turns out that the doc build process leaves a few more pyc turds now. I've updated release.py to remove them, though the script really should complain loudly if it ever finds pycs in the distribution. That'

[issue1675334] Draft implementation for PEP 364

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: Withdrawn -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.py

[issue4552] Doc/tools/sphinxext not included in the 2.6.1 tarball

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: Wait, should Doc/tools/sphinxext be included in the source tarball or not? I thought it was a documentation build artifact. If so, then we need to clean out the pycs it contains in a different way. In any case, the 3.0 tarballs

[issue4449] AssertionError in Doc/includes/mp_benchmarks.py

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: deferred blocker -> release blocker ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.py

[issue1717] Get rid of more refercenes to __cmp__

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: critical -> release blocker ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.py

[issue4561] Optimize new io library

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: high -> release blocker ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.py

[issue4565] io write() performance very slow

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: high -> release blocker ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.py

[issue4580] slicing of memoryviews when itemsize != 1 is wrong

Changes by Barry A. Warsaw : -- priority: high -> release blocker ___ Python tracker <http://bugs.python.org/issue4580> ___ ___ Python-bugs-list mailing list Un

[issue4937] Mac DMG install missing version.plist required by bundlebuilder.py

New submission from Barry Alan Scott : I installed mac python 2.6.1 on Mac OS X 10.5.6 I then ran my pysvn workbench kitting script that uses bundlebuilder.py. It fails because version.plist is not installed. Traceback (most recent call last): File "make_wb_bundle.py", l

[issue924806] email.Header.Header() produces wrong headers with utf8 enc.

Barry A. Warsaw added the comment: This isn't a bug in Python, since it does the right thing by aliasing 'utf8' with 'utf-8'. If this is incompatible with external mail tools, then you should use 'utf-8' instead, but I don't think

[issue1440472] email.Generator is not idempotent

Barry A. Warsaw added the comment: I think we should update the documentation to mention these exceptions. ___ Python tracker <http://bugs.python.org/issue1440

[issue47022] PEP 594: Document removal of asynchat, asyncore and smtpd

Change by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <https://bugs.python.org/issue47022> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue47061] Deprecate modules listed in PEP 594

Change by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <https://bugs.python.org/issue47061> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue47153] __doc__ should generally be writable

Change by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <https://bugs.python.org/issue47153> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37813] PEP 7 line-breaking with binary operations contradicts Knuth's rule

Barry A. Warsaw added the comment: I personally don't think we need to change this. C and Python are different, and the PEP 7 rules have been in place for ages. +Guido -- nosy: +gvanrossum ___ Python tracker <https://bugs.python.org/is

[issue34690] Store startup modules as C structures for 20%+ startup speed improvement

Change by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <https://bugs.python.org/issue34690> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue38010] Synchronize importlib.metadata with importlib_metadata 0.20

Change by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <https://bugs.python.org/issue38010> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue38014] Python 3.7 does not compile

Change by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <https://bugs.python.org/issue38014> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37683] Use importlib.resources in venv

Barry A. Warsaw added the comment: See also this ticket: https://gitlab.com/python-devs/importlib_resources/issues/58 We've basically agreed that you should be able to load resources from subdirectories that aren't packages. It turns out to be not a simple change in importlib

[issue38208] Simplify string.Template by using __init_subclass__()

Change by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <https://bugs.python.org/issue38208> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue38289] Add an option to point to an additional "site" directory

Change by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <https://bugs.python.org/issue38289> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue38295] macOS Catalina test failures

New submission from Barry A. Warsaw : test_py_compile fails on macOS Catalina beta (19A573a) == ERROR: test_relative_path (test.test_py_compile.PyCompileTestsWithSourceEpoch

[issue38249] Optimize out Py_UNREACHABLE in the release mode

Barry A. Warsaw added the comment: +1 Serhiy. -- ___ Python tracker <https://bugs.python.org/issue38249> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue38605] [typing] PEP 563: Postponed evaluation of annotations: enable it by default before Python 4.0

Change by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <https://bugs.python.org/issue38605> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37741] importlib.metadata docs not showing up in the module index

Barry A. Warsaw added the comment: I'd still like to. I'm also happy to review any PRs if someone beats me to it. -- ___ Python tracker <https://bugs.python.o

[issue37741] importlib.metadata docs not showing up in the module index

Barry A. Warsaw added the comment: @jaraco beat me to it. PRs approved! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue43817] Add typing.get_annotations()

Change by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <https://bugs.python.org/issue43817> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40280] Consider supporting emscripten/webassembly as a build target

Change by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <https://bugs.python.org/issue40280> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44498] move deprecated asynchat, asyncore and smtpd from the stdlib to test.support

Barry A. Warsaw added the comment: +1 for removal -- nosy: +barry ___ Python tracker <https://bugs.python.org/issue44498> ___ ___ Python-bugs-list mailin

[issue44498] move deprecated asynchat, asyncore and smtpd from the stdlib to test.support

Change by Barry A. Warsaw : -- pull_requests: +25459 pull_request: https://github.com/python/cpython/pull/26882 ___ Python tracker <https://bugs.python.org/issue44

[issue44498] add deprecation warnings for asynchat, asyncore and smtpd

Barry A. Warsaw added the comment: New changeset 8488b85c6397fe58f17fc00e047044c959ac0b04 by Barry Warsaw in branch 'main': bpo-44498: Issue a deprecation warning on asynchat, asyncore and smtpd import (#26882) https://github.com/python/cpyt

[issue44246] 3.10 beta 1: breaking change in importlib.metadata entry points

Change by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <https://bugs.python.org/issue44246> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43945] [Enum] standardize format() behavior

Change by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <https://bugs.python.org/issue43945> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33025] urlencode produces bad output from ssl.CERT_NONE and friends that chokes decoders

Change by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <https://bugs.python.org/issue33025> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44613] Make importlib.metadata non-provisional in Python 3.10

New submission from Barry A. Warsaw : As discussed with Jason, importlib.metadata will be made non-provisional in 3.10. I have a PR in the works for this. -- assignee: barry components: Documentation messages: 397344 nosy: barry, jaraco priority: normal severity: normal status: open

[issue44613] Make importlib.metadata non-provisional in Python 3.10

Change by Barry A. Warsaw : -- keywords: +patch pull_requests: +25649 stage: -> patch review pull_request: https://github.com/python/cpython/pull/27101 ___ Python tracker <https://bugs.python.org/issu

[issue44616] Incorrect tracing for "except" with variable

Change by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <https://bugs.python.org/issue44616> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44613] Make importlib.metadata non-provisional in Python 3.10

Barry A. Warsaw added the comment: New changeset f6954cdfc50060a54318fb2aea4d80408381243a by Barry Warsaw in branch 'main': bpo-44613: Make importlib.metadata non-provisional (#27101) https://github.com/python/cpython/commit/f6954cdfc50060a54318fb2aea4d80

[issue44613] Make importlib.metadata non-provisional in Python 3.10

Barry A. Warsaw added the comment: New changeset 7223ce3b3f50ec8a825e317437ea0359b6ad6856 by Miss Islington (bot) in branch '3.10': bpo-44613: Make importlib.metadata non-provisional (GH-27101) (#27106) https://github.com/python/cpython/commit/7223ce3b3f50ec8a825e317437ea03

[issue44613] Make importlib.metadata non-provisional in Python 3.10

Change by Barry A. Warsaw : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue44613] Make importlib.metadata non-provisional in Python 3.10

Barry A. Warsaw added the comment: Jason, I think the question you raise re: accelerated deprecation, is probably a RM or SC question. I'll nosy in Pablo and see if he has a strong opinion. -- nosy: +pablogsal ___ Python tracker &

[issue44616] Incorrect tracing for "except" with variable

Barry A. Warsaw added the comment: Pablo, this is triggered by my bug report here: https://github.com/nedbat/coveragepy/issues/1187 I tested this again today with the 3.10 git head and still got the coverage misses. Happy to try any other combinations

[issue44616] Incorrect tracing for "except" with variable

Barry A. Warsaw added the comment: I just retested my test case (see the coveragepy link below) with Python 3.10 git head and coveragepy git head, and I'm still seeing the misses only in Python 3.10: -- coverage: platform darwin, python 3.10.0-beta-4 ---

[issue44616] Incorrect tracing for "except" with variable

Barry A. Warsaw added the comment: Thanks Ned. Seems you might be right. I thought I'd done a clean test, but in any event, I just pulled 3.10 head and verified that it's producing 100% coverage. Thanks all for the fix! -- resolution: -> fixed status: o

[issue45155] Add default arguments for int.to_bytes()

New submission from Barry A. Warsaw : In the PEP 467 discussion, I proposed being able to use >>> (65).to_bytes() b'A' IOW, adding default arguments for the `length` and `byteorder` arguments to `int.to_bytes()` https://mail.python.org/archives/list/python-...

[issue45155] Add default arguments for int.to_bytes()

Change by Barry A. Warsaw : -- keywords: +patch pull_requests: +26685 pull_request: https://github.com/python/cpython/pull/28265 ___ Python tracker <https://bugs.python.org/issue45

[issue45155] Add default arguments for int.to_bytes()

Barry A. Warsaw added the comment: > Ah, signed=False by default, so (128).to_bytes() will work. But I still worry > that it can provoke writing more errorprone code. Can you elaborate on that? Obviously no existing code will change behavior. I really don’t expect people to write

[issue45155] Add default arguments for int.to_bytes()

Barry A. Warsaw added the comment: For the common case where you’re using all defaults, it won’t matter. byteorder doesn’t matter when length=1. > On Sep 9, 2021, at 18:12, Raymond Hettinger wrote: > > > Raymond Hettinger added the comment: > > Perhaps instead

[issue45155] Add default arguments for int.to_bytes()

Barry A. Warsaw added the comment: Just to point out, struct module also uses “native” (i.e. system) byte order by default. Any choice other than that for to_bytes() seems both arbitrary and inconsistent. > On Sep 10, 2021, at 00:48, Petr Viktorin wrote: > > Exactly, a platform-

[issue45155] Add default arguments for int.to_bytes()

Barry A. Warsaw added the comment: On Sep 10, 2021, at 04:06, STINNER Victor wrote: > > If the intent is to create a bytes string of length 1, I'm not sure that > "re-using" this existing API for that is a good idea. Why not? It seems an obviou

[issue45155] Add default arguments for int.to_bytes()

Barry A. Warsaw added the comment: Petr Viktorin added the comment: > > Exactly, a platform-dependent default is a bad idea. A default allows using > the function without the code author & reviewer even being *aware* that there > is a choice, and that is dangerous. I’m not

[issue45155] Add default arguments for int.to_bytes()

Barry A. Warsaw added the comment: That’s okay, Brandt’s improved sys.byteorder is fastest . % ./python.exe -m timeit -r11 -s 'x=3452452454524' 'x.to_bytes(10, "little")' 200 loops, best of 11: 94.6 nsec per loop % ./python.exe -m timeit -r11 -s 'x=

[issue45155] Add default arguments for int.to_bytes()

Barry A. Warsaw added the comment: I created a Discourse poll: https://discuss.python.org/t/what-should-be-the-default-value-for-int-to-bytes-byteorder/10616 -- ___ Python tracker <https://bugs.python.org/issue45

[issue45155] Add default arguments for int.to_bytes()

Barry A. Warsaw added the comment: > I'd probably say "In the face of ambiguity, refuse the temptation to guess". > > As there's disagreement about the 'correct' default, make it None and require > either "big" or "little" if len

[issue45155] Add default arguments for int.to_bytes()

Barry A. Warsaw added the comment: On Sep 13, 2021, at 13:38, STINNER Victor wrote: > It seems like your proposal is mostly guided by: convert an int to a byte > (bytes string of length 1). IMO this case is special enough to justify the > usage of a different function.

[issue45155] Add default arguments for int.to_bytes()

Barry A. Warsaw added the comment: On Sep 13, 2021, at 13:39, Vedran Čačić wrote: > > The poll is invalid, since the option that most people want is deliberately > not offered. *Is* there an option that most people want? -- ___ Pytho

[issue45155] Add default arguments for int.to_bytes()

Barry A. Warsaw added the comment: On Sep 13, 2021, at 22:12, Vedran Čačić wrote: > > > Vedran Čačić added the comment: > > I'd say yes. Of course, one way to ascertain that would be to conduct a valid > pool. ;-) People can always comment otherwise

[issue45155] Add default arguments for int.to_bytes()

Barry A. Warsaw added the comment: "big" by default -- ___ Python tracker <https://bugs.python.org/issue45155> ___ ___ Python-bugs-list mailing

[issue45202] Add 'remove_barry_from_BDFL' future to revert effects of 'from __future__ import barry_as_FLUFL'

Barry A. Warsaw added the comment: This bug made my day! :-D -- ___ Python tracker <https://bugs.python.org/issue45202> ___ ___ Python-bugs-list mailin

[issue45155] Add default arguments for int.to_bytes()

Barry A. Warsaw added the comment: New changeset 07e737d002cdbf0bfee53248a652a86c9f93f02b by Barry Warsaw in branch 'main': bpo-45155 : Default arguments for int.to_bytes(length=1, byteorder=sys.byteorder) (#28265) https://github.com/python/cpyt

[issue45155] Add default arguments for int.to_bytes()

Change by Barry A. Warsaw : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue45155] Add default arguments for int.to_bytes()

Barry A. Warsaw added the comment: On Sep 16, 2021, at 00:36, STINNER Victor wrote: > > The commit title is wrong, the default "big" not sys.byteorder: > >int.to_bytes(length=1, byteorder='big', *, signed=False) >int.from_bytes(bytes, byte

[issue45020] Freeze all modules imported during startup.

Change by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <https://bugs.python.org/issue45020> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue45324] The frozen importer should capture info in find_spec().

Change by Barry A. Warsaw : -- nosy: +barry ___ Python tracker <https://bugs.python.org/issue45324> ___ ___ Python-bugs-list mailing list Unsubscribe:

<    7   8   9   10   11   12   13   14   15   16   >