After a few days of delay, but somewhat cutely timed with the US Independence Day, I present you Python 3.8.0b2:https://www.python.org/downloads/release/python-380b2/
This release is the second of four planned beta release previews. Beta release previews are intended to give the wider community the opportunity to test new features and bug fixes and to prepare their projects to support the new feature release. The next pre-release of Python 3.8 will be 3.8.0b3, currently scheduled for 2019-07-29.Call to actionWe strongly encourage maintainers of third-party Python projects to test with 3.8 during the beta phase and report issues found to the Python bug tracker as soon as possible. While the release is planned to be feature complete entering the beta phase, it is possible that features may be modified or, in rare cases, deleted up until the start of the release candidate phase (2019-09-30). Our goal is have no ABI changes after beta 3 and no code changes after 3.8.0rc1, the release candidate. To achieve that, it will be extremely important to get as much exposure for 3.8 as possible during the beta phase.
Please keep in mind that this is a preview release and its use is not recommended for production environments.No more non-bugfixes allowed on the “3.8” branchThe time has come, team. Please help make Python 3.8 as stable as possible and keep all features not currently landed for Python 3.9. Don’t fret, it’ll come faster than you think.Media Media Media Media MediaMedia
via Python Insider https://ift.tt/2XJDstj
This release is the second of four planned beta release previews. Beta release previews are intended to give the wider community the opportunity to test new features and bug fixes and to prepare their projects to support the new feature release. The next pre-release of Python 3.8 will be 3.8.0b3, currently scheduled for 2019-07-29.Call to actionWe strongly encourage maintainers of third-party Python projects to test with 3.8 during the beta phase and report issues found to the Python bug tracker as soon as possible. While the release is planned to be feature complete entering the beta phase, it is possible that features may be modified or, in rare cases, deleted up until the start of the release candidate phase (2019-09-30). Our goal is have no ABI changes after beta 3 and no code changes after 3.8.0rc1, the release candidate. To achieve that, it will be extremely important to get as much exposure for 3.8 as possible during the beta phase.
Please keep in mind that this is a preview release and its use is not recommended for production environments.No more non-bugfixes allowed on the “3.8” branchThe time has come, team. Please help make Python 3.8 as stable as possible and keep all features not currently landed for Python 3.9. Don’t fret, it’ll come faster than you think.Media Media Media Media MediaMedia
via Python Insider https://ift.tt/2XJDstj
Python.org
Python Release Python 3.8.0b2
The official home of the Python Programming Language
We're <a href="https://pyfound.blogspot.com/search/label/pypi">further</a> increasing the security of the Python Package Index with another new beta feature: scoped API tokens for package upload. This is thanks to a <a href="https://pyfound.blogspot.com/2019/03/commencing-security-accessibility-and.html">grant from the Open Technology Fund</a>, coordinated by the <a href="https://wiki.python.org/psf/PackagingWG">Packaging Working Group</a> of the <a href="https://www.python.org/psf-landing/">Python Software Foundation</a>.
Over the last few months, we've <a href="https://pyfound.blogspot.com/2019/06/pypi-now-supports-two-factor-login-via.html">added two-factor authentication (2FA) login security methods</a>. We added Time-based One-Time Password (TOTP) support in late May and physical security device support in mid-June. Now, over 1600 users have started using physical security devices or TOTP applications to better secure their accounts. And over the past week, over 7.8% of logins to PyPI.org have been protected by 2FA, up from 3% in the month of June.
Now, we have another improvement: <a href="https://pypi.org/help/#apitoken">you can use API tokens to upload packages</a> to PyPI and <a href="https://packaging.python.org/guides/using-testpypi/">Test PyPI</a>! And we've designed the token to be a drop-in replacement for the username and password you already use (warning: this is a <b>beta feature</b> that <a href="https://wiki.python.org/psf/WarehousePackageMaintainerTesting">we need your help to test</a>).
<a href="https://1.bp.blogspot.com/-MOsRSH42y50/XUDA_d2jApI/AAAAAAAAACk/QqqWXrax4DUIl-r8VbbizQ5UouARR6vcQCPcBGAYYCw/s1600/creating-api-token-pypi.png">Add API token screen, with textarea for token name and dropdown menu to choose token scope</a>PyPI interface for adding an
API token for package upload<b>How it works: </b>Go to your <a href="https://pypi.org/manage/account/#two-factor">PyPI account settings</a> and select "Add API token". When you create an API token, you choose its scope: you can create a token that can upload to all the projects you maintain or own, or you can limit its scope to just one project.
The token management screen shows you when each of your tokens were created, and last used. And you can revoke one token without revoking others, and without having to change your password on PyPI and in configuration files.
<a href="https://1.bp.blogspot.com/-O6xLonqNBKk/XUDBANE6C4I/AAAAAAAAACs/SXcm_h6HQJgnTE24vL02GaoSmSsWrS4gACPcBGAYYCw/s1600/pypi-api-token-management.png">API token management interface displays each token's name, scope, date/time created, and date/time last used, and the user can view each token's unique ID or revoke it</a>PyPI API token management interface
Uploading with an API token is currently optional but encouraged; in the future, PyPI will set and enforce a policy requiring users with two-factor authentication enabled to use API tokens to upload (rather than just their password sans second factor). Watch <a href="https://mail.python.org/mailman3/lists/pypi-announce.python.org/">our announcement mailing list</a> for future details.
<a href="https://1.bp.blogspot.com/-TZtfwo1OgzY/XUDA_YXiHzI/AAAAAAAAACo/kc1f2ctpzowOTehr8nXCWsk5b6LN5TdKACPcBGAYYCw/s1600/pypi-api-token-just-created.png">A successful API token creation: a long string that only appears once, for the user to copy</a>Immediately after creating the API token,
PyPI gives the user one chance to copy it
<b>Why: </b>These API tokens can <b>only</b> be used to upload packages to PyPI, and not to log in more generally. This makes it safer to automate package upload and store the credential in the cloud, since a thief who copies the token won't also gain the ability to delete the project, delete old releases, or add or remove collaborators. And, since the token is a long character string (with 32 bytes of entropy and a service identifier) that PyPI has securely generated on the server side, we vastly reduce the potential for credential…
Over the last few months, we've <a href="https://pyfound.blogspot.com/2019/06/pypi-now-supports-two-factor-login-via.html">added two-factor authentication (2FA) login security methods</a>. We added Time-based One-Time Password (TOTP) support in late May and physical security device support in mid-June. Now, over 1600 users have started using physical security devices or TOTP applications to better secure their accounts. And over the past week, over 7.8% of logins to PyPI.org have been protected by 2FA, up from 3% in the month of June.
Now, we have another improvement: <a href="https://pypi.org/help/#apitoken">you can use API tokens to upload packages</a> to PyPI and <a href="https://packaging.python.org/guides/using-testpypi/">Test PyPI</a>! And we've designed the token to be a drop-in replacement for the username and password you already use (warning: this is a <b>beta feature</b> that <a href="https://wiki.python.org/psf/WarehousePackageMaintainerTesting">we need your help to test</a>).
<a href="https://1.bp.blogspot.com/-MOsRSH42y50/XUDA_d2jApI/AAAAAAAAACk/QqqWXrax4DUIl-r8VbbizQ5UouARR6vcQCPcBGAYYCw/s1600/creating-api-token-pypi.png">Add API token screen, with textarea for token name and dropdown menu to choose token scope</a>PyPI interface for adding an
API token for package upload<b>How it works: </b>Go to your <a href="https://pypi.org/manage/account/#two-factor">PyPI account settings</a> and select "Add API token". When you create an API token, you choose its scope: you can create a token that can upload to all the projects you maintain or own, or you can limit its scope to just one project.
The token management screen shows you when each of your tokens were created, and last used. And you can revoke one token without revoking others, and without having to change your password on PyPI and in configuration files.
<a href="https://1.bp.blogspot.com/-O6xLonqNBKk/XUDBANE6C4I/AAAAAAAAACs/SXcm_h6HQJgnTE24vL02GaoSmSsWrS4gACPcBGAYYCw/s1600/pypi-api-token-management.png">API token management interface displays each token's name, scope, date/time created, and date/time last used, and the user can view each token's unique ID or revoke it</a>PyPI API token management interface
Uploading with an API token is currently optional but encouraged; in the future, PyPI will set and enforce a policy requiring users with two-factor authentication enabled to use API tokens to upload (rather than just their password sans second factor). Watch <a href="https://mail.python.org/mailman3/lists/pypi-announce.python.org/">our announcement mailing list</a> for future details.
<a href="https://1.bp.blogspot.com/-TZtfwo1OgzY/XUDA_YXiHzI/AAAAAAAAACo/kc1f2ctpzowOTehr8nXCWsk5b6LN5TdKACPcBGAYYCw/s1600/pypi-api-token-just-created.png">A successful API token creation: a long string that only appears once, for the user to copy</a>Immediately after creating the API token,
PyPI gives the user one chance to copy it
<b>Why: </b>These API tokens can <b>only</b> be used to upload packages to PyPI, and not to log in more generally. This makes it safer to automate package upload and store the credential in the cloud, since a thief who copies the token won't also gain the ability to delete the project, delete old releases, or add or remove collaborators. And, since the token is a long character string (with 32 bytes of entropy and a service identifier) that PyPI has securely generated on the server side, we vastly reduce the potential for credential…
Blogspot
Python Software Foundation News
News from the Python Software Foundation
It's time for a new Python preview:
https://www.python.org/downloads/release/python-380b3/
This release is the third of four planned beta release previews. Beta release previews are intended to give the wider community the opportunity to test new features and bug fixes and to prepare their projects to support the new feature release. The next pre-release of Python 3.8 will be 3.8.0b4, the last beta release, currently scheduled for 2019-08-26.
Call to actionWe strongly encourage maintainers of third-party Python projects to test with 3.8 during the beta phase and report issues found to the Python bug tracker as soon as possible. While the release is planned to be feature complete entering the beta phase, it is possible that features may be modified or, in rare cases, deleted up until the start of the release candidate phase (2019-09-30). Our goal is have no ABI changes after beta 3 and no code changes after 3.8.0rc1, the release candidate. To achieve that, it will be extremely important to get as much exposure for 3.8 as possible during the beta phase.Please keep in mind that this is a preview release and its use is not recommended for production environments.
Last beta comingBeta 4 can only be released if all “Release blocker” and “Deferred blocker” issues on bugs.python.org for 3.8.0 are resolved. The core team will prioritize fixing those for the next four weeks.
AcknowledgementsThanks to our binary builders, Ned and Steve, who were very quick today to get the macOS and Windows installers ready. The Windows story in particular got pretty magical, it’s now really fully automatic end-to-end.
Thanks to Victor for vastly improving the reliability of multiprocessing tests since Beta 2.
Thanks to Pablo for keeping the buildbots green.Media Media Media Media MediaMedia
via Python Insider https://ift.tt/31nelKR
https://www.python.org/downloads/release/python-380b3/
This release is the third of four planned beta release previews. Beta release previews are intended to give the wider community the opportunity to test new features and bug fixes and to prepare their projects to support the new feature release. The next pre-release of Python 3.8 will be 3.8.0b4, the last beta release, currently scheduled for 2019-08-26.
Call to actionWe strongly encourage maintainers of third-party Python projects to test with 3.8 during the beta phase and report issues found to the Python bug tracker as soon as possible. While the release is planned to be feature complete entering the beta phase, it is possible that features may be modified or, in rare cases, deleted up until the start of the release candidate phase (2019-09-30). Our goal is have no ABI changes after beta 3 and no code changes after 3.8.0rc1, the release candidate. To achieve that, it will be extremely important to get as much exposure for 3.8 as possible during the beta phase.Please keep in mind that this is a preview release and its use is not recommended for production environments.
Last beta comingBeta 4 can only be released if all “Release blocker” and “Deferred blocker” issues on bugs.python.org for 3.8.0 are resolved. The core team will prioritize fixing those for the next four weeks.
AcknowledgementsThanks to our binary builders, Ned and Steve, who were very quick today to get the macOS and Windows installers ready. The Windows story in particular got pretty magical, it’s now really fully automatic end-to-end.
Thanks to Victor for vastly improving the reliability of multiprocessing tests since Beta 2.
Thanks to Pablo for keeping the buildbots green.Media Media Media Media MediaMedia
via Python Insider https://ift.tt/31nelKR
Python.org
Python Release Python 3.8.0b3
The official home of the Python Programming Language
To help you check for security problems, PyPI is adding an advanced audit log of user actions beyond the current (existing) journal. This will, for instance, allow publishers to track all actions taken by third party services on their behalf.
This beta feature is live now on PyPI and on Test PyPI.
Background:
We're further increasing the security of the Python Package Index with another new beta feature: an audit log of sensitive actions that affect users and projects. This is thanks to a grant from the Open Technology Fund, coordinated by the Packaging Working Group of the Python Software Foundation.
Details:
MediaProject security history display, listing
events (such as "file removed from release version 1.0.1")
with user, date/time, and IP address for each event.We're adding a display so you can look at things that have happened in your user account or project, and check for signs someone's stolen your credentials.
In your account settings, you can view a log of sensitive actions from the last two weeks that are relevant to your user account, and if you are an Owner at least one project on PyPI, you can go to that project's Manage Project page to view a log of sensitive actions (performed by any user) relevant to that project. (And PyPI site administrators are able to view the full audit log for all users and all projects.)
Please help us test this, and report issues.
MediaUser security history display, listing
events (such as "API token added")
with additional details (such as token scope), date/time,
and IP address for each event.In beta:
We're still refining this and may fail to log, or to properly display, events in the audit log. And the sensitive event logging and display starting on 16 August 2019, so you won't see sensitive events from before that date. (Read more technical details about implementation in the GitHub issue.)
Next:
We're continuing to refine all our beta features, while working on accessibility improvements and starting to work on localization on PyPI. Follow our progress reports in more detail on Discourse.Media Media Media Media MediaMedia
via Python Insider https://ift.tt/2KQMZq9
This beta feature is live now on PyPI and on Test PyPI.
Background:
We're further increasing the security of the Python Package Index with another new beta feature: an audit log of sensitive actions that affect users and projects. This is thanks to a grant from the Open Technology Fund, coordinated by the Packaging Working Group of the Python Software Foundation.
Details:
MediaProject security history display, listing
events (such as "file removed from release version 1.0.1")
with user, date/time, and IP address for each event.We're adding a display so you can look at things that have happened in your user account or project, and check for signs someone's stolen your credentials.
In your account settings, you can view a log of sensitive actions from the last two weeks that are relevant to your user account, and if you are an Owner at least one project on PyPI, you can go to that project's Manage Project page to view a log of sensitive actions (performed by any user) relevant to that project. (And PyPI site administrators are able to view the full audit log for all users and all projects.)
Please help us test this, and report issues.
MediaUser security history display, listing
events (such as "API token added")
with additional details (such as token scope), date/time,
and IP address for each event.In beta:
We're still refining this and may fail to log, or to properly display, events in the audit log. And the sensitive event logging and display starting on 16 August 2019, so you won't see sensitive events from before that date. (Read more technical details about implementation in the GitHub issue.)
Next:
We're continuing to refine all our beta features, while working on accessibility improvements and starting to work on localization on PyPI. Follow our progress reports in more detail on Discourse.Media Media Media Media MediaMedia
via Python Insider https://ift.tt/2KQMZq9
PyPI
PyPI · The Python Package Index
The Python Package Index (PyPI) is a repository of software for the Python programming language.
It's time for the last beta release of Python 3.8. Go find it at:
https://www.python.org/downloads/release/python-380b4/
This release is the last of four planned beta release previews. Beta release previews are intended to give the wider community the opportunity to test new features and bug fixes and to prepare their projects to support the new feature release. The next pre-release of Python 3.8 will be 3.8.0c1, the first release candidate, currently scheduled for 2019-09-30.
Call to actionWe strongly encourage maintainers of third-party Python projects to test with 3.8 during the beta phase and report issues found to the Python bug tracker as soon as possible. Please note this is the last beta release, there is not much time left to identify and fix issues before the release of 3.8.0. If you were hesitating trying it out before, now is the time.
While the release is planned to be feature complete entering the beta phase, it is possible that features may be modified or, in rare cases, deleted up until the start of the release candidate phase (2019-09-30). Our goal is have no ABI changes after beta 3 and no code changes after 3.8.0c1, the release candidate. To achieve that, it will be extremely important to get as much exposure for 3.8 as possible during the beta phase.Please keep in mind that this is a preview release and its use is not recommended for production environments.
AcknowledgmentsMany developers worked hard for the past four weeks to squash remaining bugs, some requiring non-obvious decisions. Many thanks to the most active, namely Raymond Hettinger, Steve Dower, Victor Stinner, Terry Jan Reedy, Serhiy Storchaka, Pablo Galindo Salgado, Tal Einat, Zackery Spytz, Ronald Oussoren, Neil Schemenauer, Inada Naoki, Christian Heimes, and Andrew Svetlov.
3.8.0 would not reach the Last Beta without you. Thank you!Media Media Media Media MediaMedia
via Python Insider https://ift.tt/2MN5FdO
https://www.python.org/downloads/release/python-380b4/
This release is the last of four planned beta release previews. Beta release previews are intended to give the wider community the opportunity to test new features and bug fixes and to prepare their projects to support the new feature release. The next pre-release of Python 3.8 will be 3.8.0c1, the first release candidate, currently scheduled for 2019-09-30.
Call to actionWe strongly encourage maintainers of third-party Python projects to test with 3.8 during the beta phase and report issues found to the Python bug tracker as soon as possible. Please note this is the last beta release, there is not much time left to identify and fix issues before the release of 3.8.0. If you were hesitating trying it out before, now is the time.
While the release is planned to be feature complete entering the beta phase, it is possible that features may be modified or, in rare cases, deleted up until the start of the release candidate phase (2019-09-30). Our goal is have no ABI changes after beta 3 and no code changes after 3.8.0c1, the release candidate. To achieve that, it will be extremely important to get as much exposure for 3.8 as possible during the beta phase.Please keep in mind that this is a preview release and its use is not recommended for production environments.
AcknowledgmentsMany developers worked hard for the past four weeks to squash remaining bugs, some requiring non-obvious decisions. Many thanks to the most active, namely Raymond Hettinger, Steve Dower, Victor Stinner, Terry Jan Reedy, Serhiy Storchaka, Pablo Galindo Salgado, Tal Einat, Zackery Spytz, Ronald Oussoren, Neil Schemenauer, Inada Naoki, Christian Heimes, and Andrew Svetlov.
3.8.0 would not reach the Last Beta without you. Thank you!Media Media Media Media MediaMedia
via Python Insider https://ift.tt/2MN5FdO
Python.org
Python Release Python 3.8.0b4
The official home of the Python Programming Language
Python 3.5.8rc1 is now available.
You can download Python 3.5.8rc1 here.Media Media Media Media MediaMedia
via Python Insider https://ift.tt/2A5elUd
You can download Python 3.5.8rc1 here.Media Media Media Media MediaMedia
via Python Insider https://ift.tt/2A5elUd
Python.org
Python Release Python 3.5.8rc1
The official home of the Python Programming Language
Python 3.8.0 is almost ready. After a rather tumultuous few days, we are very happy to announce the availability of the release candidate:
https://www.python.org/downloads/release/python-380rc1/
This release, 3.8.0rc1, is the final planned release preview. Assuming no critical problems are found prior to 2019-10-14, the scheduled release date for 3.8.0, no code changes are planned between this release candidate and the final release.
Please keep in mind that this is not the gold release yet and as such its use is not recommended for production environments.
Major new features of the 3.8 series, compared to 3.7Some of the new major new features and changes in Python 3.8 are:
PEP 572, Assignment expressionsPEP 570, Positional-only argumentsPEP 587, Python Initialization Configuration (improved embedding)PEP 590, Vectorcall: a fast calling protocol for CPythonPEP 578, Runtime audit hooksPEP 574, Pickle protocol 5 with out-of-band dataTyping-related: PEP 591 (Final qualifier), PEP 586 (Literal types), and PEP 589 (TypedDict)Parallel filesystem cache for compiled bytecodeDebug builds share ABI as release buildsf-strings support a handy
via Python Insider https://ift.tt/2p1lKSg
https://www.python.org/downloads/release/python-380rc1/
This release, 3.8.0rc1, is the final planned release preview. Assuming no critical problems are found prior to 2019-10-14, the scheduled release date for 3.8.0, no code changes are planned between this release candidate and the final release.
Please keep in mind that this is not the gold release yet and as such its use is not recommended for production environments.
Major new features of the 3.8 series, compared to 3.7Some of the new major new features and changes in Python 3.8 are:
PEP 572, Assignment expressionsPEP 570, Positional-only argumentsPEP 587, Python Initialization Configuration (improved embedding)PEP 590, Vectorcall: a fast calling protocol for CPythonPEP 578, Runtime audit hooksPEP 574, Pickle protocol 5 with out-of-band dataTyping-related: PEP 591 (Final qualifier), PEP 586 (Literal types), and PEP 589 (TypedDict)Parallel filesystem cache for compiled bytecodeDebug builds share ABI as release buildsf-strings support a handy
= specifier for debuggingcontinue is now legal in finally: blockson Windows, the default asyncio event loop is now ProactorEventLoopon macOS, the spawn start method is now used by default in multiprocessingmultiprocessing can now use shared memory segments to avoid pickling costs between processestyped_ast is merged back to CPythonLOAD_GLOBAL is now 40% fasterpickle now uses Protocol 4 by default, improving performance(Hey, fellow core developer, if a feature you find important is missing from this list, let Łukasz know.) Media Media Media Media MediaMediavia Python Insider https://ift.tt/2p1lKSg
Python.org
Python Release Python 3.8.0rc1
The official home of the Python Programming Language
A release candidate for the upcoming 2.7.17 bug fix release is now available for download.Media Media Media Media MediaMedia
via Python Insider https://ift.tt/2VrdI12
via Python Insider https://ift.tt/2VrdI12
Python.org
Python Release Python 2.7.17rc1
The official home of the Python Programming Language
Python 3.5.8rc2 is now available.
You can download Python 3.5.8rc2 here.Media Media Media Media MediaMedia
via Python Insider https://ift.tt/2M9Zsak
You can download Python 3.5.8rc2 here.Media Media Media Media MediaMedia
via Python Insider https://ift.tt/2M9Zsak
Python.org
Python Release Python 3.5.8rc2
The official home of the Python Programming Language