in bringing 3.6 into the world and for
helping now to make it even better!
https://www.python.org/dev/peps/pep-0494/
http://cpython-devguide.readthedocs.io
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-co
to get addressed in
3.6.2. So, I'm delaying 3.6.2rc1 until we can get that resolved. That means
that, for the moment, changes going into the 3.6 branch will likely make in
into 3.6.2. I'll let you know when we are ready to tag.
Thanks!
--Ned
On Jun 8, 2017, at 23:34, Ned Deily w
ker". To still give 2 weeks of exposure for the rc, the new target release
date for 3.6.2 final will be 2017-06-30.
--Ned
On Jun 13, 2017, at 00:09, Ned Deily wrote:
> An update on 3.6.2rc1: we have been working through a few critical and
> release blocker issues that needed to be f
nformation about the 3.6
release schedule can be found here:
https://www.python.org/dev/peps/pep-0494/
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-
.2rc2 available within the next couple of
days (2017-07-04 expected) and, assuming no new issues, 3.6.2 final about a we
ek later (around 2017-07-11).
--Ned
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-committers@pytho
e-2
3.6.2 is now planned for final release on 2017-07-17 with the next
maintenance release expected to follow in about 3 months. More
information about the 3.6 release schedule can be found here:
https://www.python.org/dev/peps/pep-0494/
--
Ned Deily
n...@
substantial performance improvements await you.
https://www.python.org/dev/peps/pep-0398/
https://devguide.python.org/devcycle/#security-branches
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-committers@python.org
https:
The most current updated versions will appear here:
https://docs.python.org/3.6/
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Cond
is needed when building the docs directly from the Git repo, including the
daily website builds, but it should not be performed when building the Docs
from a release tarball. Please open an issue for this on the tracker and mark
it as "release blocker" so it can get so
://www.python.org/downloads/release/python-337rc1/
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf
process and to make it easier for Windows and
Macs users to help test. Many new features and build changes are yet to appear
in subsequent releases prior to feature code cutoff on 2018-01-29 at 3.7.0b1.
Thanks for your help!
--Ned
--
Ned Deily
out it, please contact me directly. AFAIK,
there is no other release calendar feed currently.
--
Ned Deily
n...@python.org -- []
> On Sep 13, 2017, at 09:57, Fred Drake wrote:
>
>> On Wed, Sep 13, 2017 at 12:35 PM, Ned Deily wrote:
>> Lots of releases coming up so
On Sep 19, 2017, at 13:55, Terry Reedy wrote:
> On 9/13/2017 12:35 PM, Ned Deily wrote:
>
>> 2017-09-18 1200 UTC cutoff:
>> - Python 3.6.3 rc1
>
>> Also on 2017-09-18:
>> - Python 3.7.0 alpha 1
>
> Have you branched these off so that further merges go
ing system
releases and some tests may fail. If you are still using Python 3.3.x,
we **strongly** encourage you to upgrade now to a more recent, fully
supported version of Python 3. You can find Python 3.3.7 here:
https://www.python.org/downloads/release/python-337/
--
Ned Deily
n...@
The next maintenance release of Python 3.6 is expected to follow in
about 3 months, around the end of 2017-12. More information about the
3.6 release schedule can be found here:
https://www.python.org/dev/peps/pep-0494/
Enjoy!
--
Ned Deily
n...@
a preview release and its use is not recommended for
production environments. The next preview, 3.7.0a3, is planned for
2017-11-27. You can find Python 3.7.0a2 and more information here:
https://www.python.org/downloads/release/python-370a2/
--
Ned Deily
n...@python.org
ing
efforts!
--Ned
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/
maintenance release release
candidate, 3.6.4rc1. So I hope you can take advantage of the extra days for
both release cycles.
Thanks again for all your efforts!
--Ned
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python
adequately reviewed and
ready to go, go for it; likewise for normal bug fixes and doc changes. But
keep in the mind that there is still one more alpha preview release coming
prior to the beta 1 feature code freeze, so no need to panic.
--
Ned Deily
n...@python.org
/
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/
ribe to
> python-committers mailing list :)
It should all be here in the Devguide:
https://devguide.python.org/coredev/#gaining-commit-privileges
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-committers@python.org
uot;. In other words, some people would do a fine job as
triager without wanting to be a core developer or contributing their own code
patches, and that's fine.
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-com
doc infrastructure, processes, and the people
who work on them. I've found him to be easy to work with and to display good
judgement. I would be very happy to see Julien take on a more formal role with
our documentation process and any other area that he would like to get involved
with.
The next maintenance release of Python 3.6 is expected to follow in
about 3 months, around the end of 2018-03. More information about the
3.6 release schedule can be found here:
https://www.python.org/dev/peps/pep-0494/
Enjoy!
--
Ned Deily
n...@
preview release and its use is not recommended for
production environments. The next preview release, 3.7.0b1, is planned
for 2018-01-29. You can find Python 3.7.0a4 and more information here:
https://www.python.org/downloads/release/python-370a4/
--
Ned Deily
n...@python.org
all the way at the bottom, generated by blurb:
Misc/NEWS.d/next/Library/2018-01-04-14-45-33.bpo-29237.zenYA6.rst
https://github.com/python/cpython/pull/5103/files
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/
https://www.python.org/dev/peps/pep-0537/
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf
) are unaffected.
Thanks for your patience!
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/
candidates for cherry picking after the branch
> is created so that we don't miss any? Otherwise I fear we may
> end up with some bug fixes that get in to 3.8 and 3.6 but not 3.7.
Hang tight, I'm working on that right at this moment :) Almost ready!
-
On Jan 31, 2018, at 16:14, Ned Deily wrote:
> Hang tight, I'm working on that right at this moment :) Almost ready!
FYI, I'm going to lock the master branch for a brief period starting right now
to do the cutover to 3.8. I'll let you know when it's unlocked.
--
Ned
Here we are: 3.7.0b1 and feature code freeze! Congratulations and
thanks to all of you who've contributed to the huge number of PEPs,
features, bug fixes, and doc changes that have gone into 3.7 since
feature development began back in September 2016, after 3.6.0b1,
3.6's feature freeze. Now that fe
n be found here:
https://www.python.org/dev/peps/pep-0537/
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www
after 3.7.0b3 without further discussion.
Thanks again for all of your hard work towards making 3.7.0 yet another
great release!
--Ned
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-committers@python.org
https://mail.pytho
nd here:
https://www.python.org/dev/peps/pep-0537/
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/
018-12, 6 months after 3.7.0 releases and 2 years after 3.6.0 first released.
Thereafter, only security issues will be accepted and addressed for the
remaining life of 3.6.
Thanks again!
--Ned
https://www.python.org/dev/peps/pep-0494/
--
/release/python-365rc1/
Attention macOS users: as of 3.6.5rc1, there is a new additional installer
variant for macOS 10.9+ that includes a built-in version of Tcl/Tk 8.6.
This variant is expected to become the default variant in future releases.
Check it out!
--
Ned Deily
n...@python.org
ing PRs
for 3.7 (and please do!), be on the lookout for and flag potential
incompatibilities (we've all made them).
Thanks again for all of your hard work towards making 3.7.0 yet
another great release!
--Ned
--
Ned Deily
n...@python.org -- []
___
https://www.python.org/psf/
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/
ore information about the release schedule
can be found here:
https://www.python.org/dev/peps/pep-0537/
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/py
potential incompatibilities (we've all
made them).
Thanks again for all of your hard work towards making 3.7.0 yet
another great release - coming to a website near you on 06-15!
--Ned
--
Ned Deily
n...@python.org -- []
___
python-committers m
out!
The next preview release will be the release candidate and is planned
for 2018-05-21 followed by the official release of 3.7.0, planned for
2018-06-15. You can find Python 3.7.0b4 and more information here:
https://www.python.org/downloads/release/python-370b4/
--
Ned Deily
n...@python.org
o!), be on
the lookout for and flag potential incompatibilities (we've all made
them).
Thanks again for all of your hard work towards making 3.7.0 yet
another great release - coming to a website near you on 06-15!
Release Managerly Yours,
--Ned
https://www.python.org/de
Elvis has been working on the What’s New doc at the sprints this week. He
should be checking in his edits soon. Stay tuned!
--
Ned Deily
n...@python.org -- []
> On May 17, 2018, at 14:31, Serhiy Storchaka wrote:
>
> 15.05.18 14:51, Ned Deily пише:
>> This is it!
07:51, Ned Deily wrote:
> This is it! We are down to THE FINAL WEEK for 3.7.0! Please get your
> feature fixes, bug fixes, and documentation updates in before
> 2018-05-21 ~23:59 Anywhere on Earth (UTC-12:00). That's about 7 days
> from now. We will then tag and produce the 3.7.0 re
On May 23, 2018, at 07:45, Serhiy Storchaka wrote:
> 15.05.18 14:51, Ned Deily пише:
>> This is it! We are down to THE FINAL WEEK for 3.7.0! Please get your
>> feature fixes, bug fixes, and documentation updates in before
>> 2018-05-21 ~23:59 Anywhere on Earth (UTC-12:00)
On May 23, 2018, at 09:13, Ned Deily wrote:
> On May 23, 2018, at 07:45, Serhiy Storchaka wrote:
>> Is it possible to add yet one beta instead?
>> CI was broken for few latest days, tests are not passed on my computer still
>> (and fail on some buildbots), updating W
On May 24, 2018, at 07:26, Victor Stinner wrote:
> 2018-05-24 9:23 GMT+02:00 Ned Deily :
>> Any merges to the 3.7 branch after
>> that will be released in 3.7.1 which we tentatively are planning to
>> ship sometime before the end of July (< 2018-07-31).
> I recall th
ase blocker"?
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/
On May 24, 2018, at 12:26, Serhiy Storchaka wrote:
> 24.05.18 19:02, Ned Deily пише:
>> On May 24, 2018, at 11:35, Serhiy Storchaka wrote:
>>> I have doubts about two issues. I feel the responsibility for them because
>>> I had the opportunity to solve
On May 24, 2018, at 13:46, Larry Hastings wrote:
> On 05/24/2018 10:08 AM, Ned Deily wrote:
>> If you (or anyone else) feels strongly enough about it, you should re-open
>> the issue now and make it as a "release blocker" and we should discuss the
>> implications
On May 24, 2018, at 03:23, Ned Deily wrote:
> On May 23, 2018, at 09:13, Ned Deily wrote:
>> On May 23, 2018, at 07:45, Serhiy Storchaka wrote:
>>> Is it possible to add yet one beta instead?
>>> CI was broken for few latest days, tests are not passed on my computer
gt;
> > For example my PR https://github.com/python/cpython/pull/7120 which
> > changes Lib/test/regrtest.py cannot be merged because a commit
> > touching the documentation (Doc/ directory) has been merged after I
> > posted my PR and before the CI completed.
> >
> > I
time to work on making
Python better. I, for one, am deeply grateful.
2018-05-30 3.7.0b5
2018-06-11 3.7.0rc1 & 3.6.6rc1
2018-06-27 3.7.0final & 3.6.6final
--Ned
On May 25, 2018, at 01:33, Ned Deily wrote:
> On May 24, 2018, at 03:23, Ned Deily wrote:
>> On May 23, 2018, at 0
On May 29, 2018, at 17:45, R. David Murray wrote:
> At Yuri's request I've given Elvis triage privileges on the tracker.
> I don't anticipate any objections, given the work he's done on
> What's New and other things.
+1
Thanks!
ense to me.
So, I really really don't think there's a problem today that needs solving and,
worse, the suggestions so far add complexity with no benefit at all as far as I
can see. May I respectfully suggest that we just drop this discussion and move
on, please?
--
Ned Deily
n...
06-11, followed by the official
release of 3.7.0, now planned for 2018-06-27. You can find Python 3.7.0b5
and more information here:
https://www.python.org/downloads/release/python-370b5/
--
Ned Deily
n...@python.org -- []
___
python-committers ma
ws CI runs
as well. That, along with a number of other test fixes made over the past
week, may help eliminate with AppVeyor. But, at this point, I think we should
seriously consider dropping mandatory AppVeyor CI runs in favor of the VSTS
ones.
Brett, do you concur? And, if so, can
r
> others. I will be extra careful and only change those when I'm very sure it
> is appropriate.
>
> Can the necessary permission bits be flipped?
You should be good to go now. Welcome to the tracker!
--
Ned Deily
n...@python.org -- []
__
and buildbot test failures and see if you can help
resolve them. As always, if you think you may have found a critical
problem at any time in either release candidate, please open (or reuse)
an issue on bugs.python.org and mark it as "release blocker" priority.
3.7.0: here we c
06-27 3.7.0 final !!! and 3.6.6 final !!
- 2018-07-xx 3.7.1
- 2018-09-xx 3.6.7
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduc
://www.python.org/downloads/release/python-366rc1/
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf
nch during the release process, which is much
> nicer. If you wanted something in 3.7.0 you would have to mark as release
> blocker and be very persuasive that he should cherry-pick into the 3.7.0
> release branch.
Thanks, Terry, that description is exactly right.
--
Ned Deily
n...
, for example when trying to
merge a PR, please try again in a few hours.
Thanks and more later!
https://bugs.python.org/issue33851
https://bugs.python.org/issue33932
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python
the
Python Software Foundation.
https://www.python.org/psf/
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Cond
is earlier (or maybe I'm projecting): who's to say that the
> next BDFL is legitimate? If we put together a plan, and Guido blesses it,
> that makes the plan legitimate, and then the plan gets executed and makes
> NBDFL legitimate.
That, too.
--
Ned Deily
n...@pytho
lease ensure there are open issues for
them in the bug tracker (bugs.python.org) and that their priorities are set
accordingly (e.g. "release blocker").
Thanks for your support!
--Ned
--
Ned Deily
n...@python.org -- []
___
python-committe
g the important ones
resolved so I'm going to plan on cutting off code for 3.7.1rc1 and 3.6.7rc1 by
the end of 2018-09-20 (23:59 AoE). That's roughly 38 hours from now.
Thanks for all of your help in improving Python for everyone!
--Ned
On Sep 10, 2018, at 18:17, Ned Deily wrote:
> I ha
On Sep 21, 2018, at 05:37, Christian Heimes wrote:
> On 19/09/2018 23.12, Ned Deily wrote:
>> Update: not surprisingly, there have been a number of issues that have
>> popped up during and since the sprint that we would like to ensure are
>> addressed in 3.7.1 and 3.6.
-371rc1/
https://www.python.org/downloads/release/python-367rc1/
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https
buildbot exposure and potential exposure in the wider
community.
Thanks!
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https
/python-371rc2/
https://www.python.org/downloads/release/python-367rc2/
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct
Python Development and
these releases possible! Please consider supporting our efforts by
volunteering yourself or through organization contributions to the Python
Software Foundation.
--
Ned Deily
n...@python.org -- []
___
python-committers mailing
https://discuss.python.org/t/julien-palard-joins-the-python-release-team-as-documentation-expert/313
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python
/devguide.python.org/#branchstatus
https://www.python.org/dev/peps/pep-0494/
https://www.python.org/dev/peps/pep-0537/
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/
On Dec 4, 2018, at 03:42, Ned Deily wrote:
> https://discuss.python.org/t/3-7-2rc1-and-3-6-8rc1-cutoffs-ahead-last-3-6-x-bugfix-release/510
An update: as of the planned Friday cutoff, we still had a few open issues.
Since 3.6.8 is the last planned bugfix for the 3.6 branch, I would like
your help!
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/
releases and more information here:
https://www.python.org/downloads/release/python-372rc1/
https://www.python.org/downloads/release/python-368rc1/
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-committers
tments now. And it's
not something that I as release manager or any of us individually as core
developers can or should do.
--Ned
P.S. Thanks for bringing this up, Serihy, and thanks for everyone's
thoughtful responses.
-- Ned Deily
n...@python.org -- []
_
#python-3-7-2-final
https://docs.python.org/3.6/whatsnew/changelog.html#python-3-6-8-final
https://www.python.org/psf/
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman
produces a valid
changelog with a local docs build. I don't see anything odd on the GitHub end
of things. Perhaps Mariatta can take a look at the Bevedere end?
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
python-commi
ed?
Possibly, if you modified the news entry while the other CI checks were still
running? I guess you could force the whole CI process to run again by closing
and re-opening the PR. Or a release manager could override it with an
appropriate b
not a bug? :)
https://blog.codinghorror.com/web-discussions-flat-by-design/
--
Ned Deily
n...@python.org -- []___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/
issue as a release blocker prior to 3.7.3 final, planned for 2019-03-25, and
explain why the change should be cherry-picked into the final release.
https://www.python.org/dev/peps/pep-0537/
--
Ned Deily
n...@python.org -- []
___
python
recommended for
production environments.
You can find the release files, a link to the changelog, and more
information here:
https://www.python.org/downloads/release/python-373rc1/
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list
possible! Please consider supporting our efforts by
volunteering yourself or through organization contributions to the Python
Software Foundation.
https://docs.python.org/3.7/whatsnew/3.7.html
https://docs.python.org/3.7/whatsnew/changelog.html#python-3-7-3-final
https://www.python.org/psf/
--
Ned
3.7.x bugfix releases every three
months until 2020-06-27, two years after the initial release of 3.7.0. At
that point, 3.7.x will enter its security-fix-only phase for an
additional three years.
https://www.python.org/dev/peps/pep-0537/
--
Ned Deily
n...@python.org -- []
python-committers ma
/release/python-374rc1/
https://www.python.org/downloads/release/python-369rc1/
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
hanges to it. Prior to the release cutoff,
you can modify the individual file in Misc/NEWS.d/next. Don't forget to make
similar changes as necessary to any backported PRs!
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list --
On Jun 6, 2019, at 01:43, Ned Deily wrote:
>
> https://discuss.python.org/t/python-3-7-4rc1-and-3-6-9rc1-cutoffs-ahead-now-set-for-2019-06-17/1824
> [...]
> Following the rc1 cutoff, changes merged to the
> 3.7 branch will be released in 3.7.5 three months from now unless you
>
ld!
P.S. Now that we are over this hump, expect to see 3.8.0b2 real soon now.
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.or
changelog, and more
information here:
https://www.python.org/downloads/release/python-374rc2/
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le
can find the release files, a link to the changelog, and more
information here:
https://www.python.org/downloads/release/python-369/
https://www.python.org/downloads/
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list -- python
on.org/3.7/whatsnew/3.7.html
Thanks to all of the many volunteers who help make Python Development and
these releases possible! Please consider supporting our efforts by
volunteering yourself or through organization contributions to the Python
Software Foundation:
https://www.python.org/psf/
--
itish Summer Time,
at that).
https://www.python.org/dev/peps/pep-0537/
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
][CVE-2019-9947] HTTP Header Injection (follow-up of
CVE-2016-5699)
https://bugs.python.org/issue36274
http.client cannot send non-ASCII request lines
On Sep 9, 2019, at 07:10, Ned Deily wrote:
> https://discuss.python.org/t/3-7-5rc1-cutoff-ahead/2288
>
> A reminder: it is tim
/peps/pep-0569/
https://www.python.org/dev/peps/pep-0478/
https://www.python.org/dev/peps/pep-0373/
https://bugs.python.org
On Sep 17, 2019, at 19:26, Ned Deily wrote:
> 2019-09-17 Update: as of the scheduled cutoff time earlier today, we had two
> recently identified release blocker issue
recommended for production
environments.
You can find the release files, a link to the changelog, and more information
here:
https://www.python.org/downloads/release/python-375rc1/
--
Ned Deily
n...@python.org -- []
___
python-committers mailing
.
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message
urity branch criteria:
https://devguide.python.org/devcycle/#security-branches
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
Details here:
https://discuss.python.org/t/python-3-7-6rc1-and-3-6-10rc1-are-now-available-for-testing/2835
https://www.python.org/downloads/release/python-376rc1/
https://www.python.org/downloads/release/python-3610rc1/
--
Ned Deily
n...@python.org
1 - 100 of 231 matches
Mail list logo
