bpo-38021: Provide a PEP425 platform tag with sufficient detail for pypa packaging#15678
bpo-38021: Provide a PEP425 platform tag with sufficient detail for pypa packaging#15678aixtools wants to merge 749 commits into
Conversation
|
Another bit I am adding - so it is central, rather than being repeated in everything that needs it makes the following simple program possible. from sysconfig import get_platform as get_platform from _aix_support import aix_buildtag as get_btag print("running:{!s}".format(get_platform())) On system it was built on: root@x066:[/data/prj/python/python3-3.9]./python ../git/aix_build_tag.py On AIX 6.1 TL9 system michael@x071:[/data/prj/python/python3-3.9]./python ../git/aix_build_tag.py On AIX 7.1 TL4 system root@x064:[/data/prj/python/python3-3.9]./python ../git/aix_build_tag.py |
|
https://bugs.python.org/issue38021 msg351332 for details on the last change |
…ythonGH-16536) pathfix.py: Assume all files that end on '.py' are Python scripts when working recursively.
…er parsing of URLs (pythonGH-15522)" (pythonGH-16724) This reverts commit 87bd207. https://bugs.python.org/issue38449
Since `smtpd.MailmanProxy` is already broken, it is not formally deprecated in 3.9. It will be removed in 3.10. https://bugs.python.org/issue35800
This is a fairly noticeable change that requires adjustments in existing asyncio code. It should therefore be announced.
On POSIX systems, allow the umask to be set in the child process before we exec.
* bpo-38456: Use /bin/true in test_subprocess. Instead of sys.executable, "-c", "pass" or "import sys; sys.exit(0)" use /bin/true when it is available. On a reasonable machine this shaves up to two seconds wall time off the otherwise ~40sec execution on a --with-pydebug build. It should be more notable on many buildbots or overloaded slower I/O systems (CI, etc).
…GH-16742) They conflicted with keyword "in". Also rename positional-only parameters of private os._fcopyfile() for consistency.
…jects resurrect (pythonGH-16687) Currently if any finalizer invoked during garbage collection resurrects any object, the gc gives up and aborts the collection. Although finalizers are assured to only run once per object, this behaviour of the gc can lead to an ever-increasing memory situation if new resurrecting objects are allocated in every new gc collection. To avoid this, recompute what objects among the unreachable set need to be resurrected and what objects can be safely collected. In this way, resurrecting objects will not block the collection of other objects in the unreachable set.
* Use Unicode character for accent * Various grammar fixes * Sort library modules alphabetically; remove duplicated idlelib/IDLE section
…ocs (pythonGH-16743) Metaclass was removed in Python 3.7 (there is already a `versionchanged` item about this). https://bugs.python.org/issue28556
* Misc gc code & comment cleanups. validate_list: there are two temp flags polluting pointers, but this checked only one. Now it checks both, and verifies that the list head's pointers are not polluted. move_unreachable: repaired incoherent comments. Added new comments. Cleared the pollution of the unreachable list head's 'next' pointer (it was expedient while the function was running, but there's no excuse for letting this damage survive the function's end). * Update Modules/gcmodule.c Co-Authored-By: Pablo Galindo <Pablogsal@gmail.com>
pythonGH-16755) The symbol table handing of PEP572's assignment expressions is not resolving correctly the scope of some variables in presence of global/nonlocal keywords in conjunction with comprehensions.
|
Something is drastically wrong here. |
|
I am not sure what you did today or before, but this includes all idlelib changes since early September (about when this was opened). Perhaps the root problem is that your aixtools/cpython fork master branch is also '3 months' out of date. My suggestion: delete aixtools:bpo-38021-pep425 from your github fork, but not locally. Update local master from python/cpython and push updated master to your fork. Checkout local aixtools:bpo-38021-pep425 branch (assuming that it was properly created from master). Do an update merge: 'git merge origin/master. Push the branch to your fork. Hit the compare button to create a new PR. Stop and check the diff to make sure it only contains your changes or other changes that belong to the PR. Only make new PR if this is true. If it contains extraneous diffs from already merged PR, figure out fix or ask on core-mentorship. |
|
I tried to rebase. Sigh. |
https://bugs.python.org/issue38021
Think tools such as pypa/pip, pypa/wheel, and in the future pypa/packaging