[Python-Dev] Re: Have a big machine and spare time? Here's a possible Python bug.
I have only 32 GB. http://nortonkeysetup.com ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/4M7KGZQV3PVAUL7L6VP7NRE3E7RBWE6K/
[Python-Dev] Summary of Python tracker Issues
ACTIVITY SUMMARY (2019-07-12 - 2019-07-19) Python tracker at https://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open7111 (+12) closed 42272 (+47) total 49383 (+59) Open issues with patches: 2877 Issues opened (41) == #28292: Make Calendar.itermonthdates() behave consistently in edge cas https://bugs.python.org/issue28292 reopened by rhettinger #34443: enum repr should use __qualname__ https://bugs.python.org/issue34443 reopened by ethan.furman #37574: Mention spec_from_loader() in Finder.find_spec() docs. https://bugs.python.org/issue37574 opened by eric.snow #37575: Python Documentation on strings (tutorial section 3.1.2.) https://bugs.python.org/issue37575 opened by Deshpande #37577: ModuleNotFoundError: No module named '_sysconfigdata__linux_x8 https://bugs.python.org/issue37577 opened by luisalejandro #37578: Change Glob: Allow Recursion for Hidden Files https://bugs.python.org/issue37578 opened by k64 #37581: Docs: Improve phrasing of flush argument for print() https://bugs.python.org/issue37581 opened by aeros167 #37583: Got a 113 error when running the test_socket https://bugs.python.org/issue37583 opened by shihai1991 #37584: Multiple test failures with OSError: [Errno 84] Invalid or inc https://bugs.python.org/issue37584 opened by dimitern #37586: macOS: posix_spawn(..., setsid=True) https://bugs.python.org/issue37586 opened by ronaldoussoren #37587: JSON loads performance improvement for long strings https://bugs.python.org/issue37587 opened by mpaolini #37588: Py_DEPRECATED and unavoidable warnings https://bugs.python.org/issue37588 opened by philthompson10 #37589: Missing dependences in the Makefile https://bugs.python.org/issue37589 opened by vemakereporter #37591: test_concurrent_future failed https://bugs.python.org/issue37591 opened by Martin Bammer #37592: sysconfig should not rely on sys.version https://bugs.python.org/issue37592 opened by carlbordum #37595: Python 3.7.4 does not build on Raspbian Buster https://bugs.python.org/issue37595 opened by kal.sze #37596: Reproducible pyc: frozenset is not serialized in a determinist https://bugs.python.org/issue37596 opened by vstinner #37597: audit event table breaks PDF sphinx build https://bugs.python.org/issue37597 opened by mdk #37601: shutil.make_archive does not follow symlinks for zip archives https://bugs.python.org/issue37601 opened by Kevin Teague #37602: nonzero fixer problem https://bugs.python.org/issue37602 opened by shiyuchong #37603: parsetok(): Assertion `(intptr_t)(int)(a - line_start) == (a - https://bugs.python.org/issue37603 opened by vstinner #37604: warnings should use a ContextVar to manage filters/registry https://bugs.python.org/issue37604 opened by graingert #37605: CI should not depend on gmane response https://bugs.python.org/issue37605 opened by terry.reedy #37607: segfault running code in jupyter on macOS 10.14.5 - crashed on https://bugs.python.org/issue37607 opened by wesinator #37608: _thread: acquire_lock,release_lock still in use while declared https://bugs.python.org/issue37608 opened by shiyuchong #37609: support "UNC" device paths in ntpath.splitdrive https://bugs.python.org/issue37609 opened by eryksun #37611: Improve the "Dealing with Bugs" documentation, include guideli https://bugs.python.org/issue37611 opened by Mariatta #37612: os.link(..., follow_symlinks=True) broken on Linux https://bugs.python.org/issue37612 opened by jo-he #37616: [3.10 prep] zip path incorrect https://bugs.python.org/issue37616 opened by Anthony Sottile #37618: Docs: Code example locations in stdtypes https://bugs.python.org/issue37618 opened by aeros167 #37619: update_one_slot() should not ignore wrapper descriptors for wr https://bugs.python.org/issue37619 opened by jdemeyer #37620: str.split(sep=None, maxsplit=-1,any=False) https://bugs.python.org/issue37620 opened by hcoin #37621: Line continuation of blank line emits NEWLINE https://bugs.python.org/issue37621 opened by miedzinski #37622: Signature of SHA256 HMAC digest not matching with the signatur https://bugs.python.org/issue37622 opened by dodain #37623: namedtuple integration for importlib.abc.Loader https://bugs.python.org/issue37623 opened by captain-kark #37626: Documentationï¼conflict between docs https://bugs.python.org/issue37626 opened by shiyuchong #37627: Minor improvements to IDLE's "Run Customized" https://bugs.python.org/issue37627 opened by rhettinger #37628: IDLE Font Sample distracting and too large https://bugs.python.org/issue37628 opened by rhettinger #37630: Investigate replacing SHA3 code with OpenSSL https://bugs.python.org/issue37630 opened by christian.heimes #37631: EXTRA_CFLAGS get overrided by CFLAGS_NODIST https://bugs.python.org/issue37631 opened by Dormouse759 #37632: generator expression doesn't find subclass https://bug
[Python-Dev] Re: Long-term deprecation policy
On Wed, Jul 17, 2019 at 2:36 AM Brett Cannon wrote: > > Jeroen Demeyer wrote: > > I have seen multiple discussions where somebody wants to deprecate a > > useless function but somebody else complains that we cannot do that > > because the function in question cannot be removed (because of backwards > > compatibility). See https://bugs.python.org/issue29548... for an > > example. > > We currently have a deprecation policy saying that functions deprecated > > in version N cannot be removed before version N+2. > > Do we have that officially written down anywhere? The closest I know is > https://www.python.org/dev/peps/pep-0387/ but that PEP is still a draft. > > And for me the "official" policy is if you deprecate in N you can remove in > N+1, not N+2. (But all of this is a bit wonky with Python 2.7 still being > alive and not being able to remove anything from the stdlib unless it's > severely broken until 2.7 hits EOL). > See also https://mail.python.org/archives/list/python-dev@python.org/thread/ZUKVACWVX7SQEA7FGZRXALR7PWCLV7K6/ Some things changed since that thread, but some points are still valid. > > That's a reasonable > > policy but some deprecation purists insist that it MUST (instead of MAY) > > be removed in version N+2. Following this reasoning, we cannot deprecate > > something that we cannot remove. > > Personally, I think that this reasoning is flawed: even if we cannot > > remove a function, we can still deprecate it. That way, we send a > > message that the function shouldn't be used anymore. And it makes it > > easier to remove it in the (far) future: if the function was deprecated > > for a while, we have a valid reason to remove it. The longer it was > > deprecated, the less likely it is to be still used, which makes it > > easier to remove eventually. > > So I suggest to embrace such long-term deprecations, where we deprecate > > something without planning in advance when it will be removed. This is > > actually how most other open source projects that I know handle > > deprecations. > > I'd like to know the opinion of the Python core devs here. > > I prefer removal for ease of maintenance (people always want to update code > even if it's deprecated), and to help make sure people who don't read the > docs but discover something via the REPL or something and don't run with > warnings on do not accidentally come to rely on something that's deprecated. > ___ > Python-Dev mailing list -- python-dev@python.org > To unsubscribe send an email to python-dev-le...@python.org > https://mail.python.org/mailman3/lists/python-dev.python.org/ > Message archived at > https://mail.python.org/archives/list/python-dev@python.org/message/PRI2O6G6O6HUVGXD3W2MSCEF4JTW36IB/ ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/GQDFRX3K6DIWYSRZNAW2AIOUCGHSZWA4/
