ar future
(likely by the end of 2022). So, eventually x86_64-apple-darwin will fade in
importance as older Macs are retired but that will take many years.
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list -- python-committers@pyth
if you haven't already, you may want to update your repo
clones with "git fetch --tags upstream" (if you use the recommended naming
convention) to get the latest tags and branches.
--
Ned Deily
n...@python.org -- []
___
python-com
[Retransmit]
Python 3.7.12 and 3.6.15, the lastest security fix rollups for Python 3.7 and
Python 3.6, are now available. You can find the release files, links to the
changelogs, and more information here:
https://www.python.org/downloads/release/python-3712/
https://www.python.org/download
technical skills, his
judgement, and his obvious passion for Python. It's been a pleasure working
with him so far and I look forward to his contributions in this new role over
the coming months.
Woot!
--Ned
--
Ned Deily
n...@python.org -- []
___
to do it and the only obvious
reason for doing it is to stop these discussions. And that hasn't been
motivation yet enough given the list of higher priority items.
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list -- pyth
es/1227. It will also require
co-ordination with release managers as we are the ones who populate the data,
if anyone feels motivated to dig into the webside code.
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list -- python-co
://www.python.org/psf-landing/
--
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
issues that should be
addressed in these releases, please mark the relevant bpo issues as "release
blocker" and, if possible, submit PRs for review prior to the end of 2021-01-14
AOE.
Thanks!
--
Ned Deily
n...@python.org -- []
signature.asc
Description: Message signed wi
of much more value, I
think.
>
>> On Sat, Dec 19, 2020 at 1:41 PM Ned Deily wrote:
>>
>> On Dec 19, 2020, at 14:57, joannah nanjekye
>> wrote:
>> > I got to know from Pablo that the release process is documented in a PEP
>> > here: https://www.pyth
uide. It could certainly be improved. Are there some things
in particular of value to core developers that are missing or could use work
there?
--
Ned Deily
n...@baybryj.net -- []
signature.asc
Description: Message signed with OpenPGP
___
python-com
that is about to change somewhat anyway
thanks to Pablo's work at further automating the process), and with who to
contact if one is interested in becoming a release manager for a future release
(today, that would be the current and past release managers).
> On Sat, Dec 19, 2020 at 5:22
could certainly be improved. Are there some things
in particular of value to core developers that are missing or could use work
there?
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list -- python-committers@python.org
To unsu
On Oct 19, 2020, at 14:35, Brett Cannon wrote:
> On Mon, Oct 19, 2020 at 11:22 AM Ned Deily wrote:
>> On Oct 19, 2020, at 13:59, Brett Cannon wrote:
>> > On Sun, Oct 18, 2020 at 2:21 PM Ethan Furman wrote:
>> >> On 10/18/20 1:18 PM, Ned Deily wrote:
>> &
On Oct 19, 2020, at 13:59, Brett Cannon wrote:
> On Sun, Oct 18, 2020 at 2:21 PM Ethan Furman wrote:
>> On 10/18/20 1:18 PM, Ned Deily wrote:
>> > On Oct 18, 2020, at 15:45, Carol Willing wrote:
>> >> We've largely moved away from Travis for Jupyter testing
vis CI results,
perhaps we should consider being "good citizens" and stop running them all
together. Each PR change triggers multiple builds to run under Travis and all
that extra and useless work contributes to the load on Travis and no doubt is
not good for overall Travis responsiven
releases is small.
Core developers: if you know of any additional security issues that should be
addressed in these releases, please mark the relevant bpo issues as "release
blocker" and, if possible, submit PRs for review prior to the end of 2020-08-13
AOE. Thanks!
--
Ned Deily
n...@
https://discuss.python.org/t/python-3-7-8-and-3-6-11-now-available-last-3-7-x-bugfix-release/4583
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers
Details here:
https://discuss.python.org/t/python-3-7-8rc1-and-3-6-11rc1-are-now-available-for-testing/4467
https://www.python.org/downloads/release/python-378rc1/
https://www.python.org/downloads/release/python-3611rc1/
--
Ned Deily
n...@python.org
. Assuming no
release-blocker issues arise during the release candidate testing, 3.7.8 and
3.6.11 will release on 06-27.
https://discuss.python.org/t/upcoming-cutoffs-for-3-9-3-8-3-7-and-3-6-releases-last-chance-for-3-7-bugfixes/4362
--
Ned Deily
n...@python.org
https://discuss.python.org/t/upcoming-cutoffs-for-3-9-3-8-3-7-and-3-6-releases-last-chance-for-3-7-bugfixes/4362
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to
per role and this is
> my first time running into anything like this.
No problem! We all have learning events along the way. Keep hacking!
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list -- python-committers@python.org
To u
On May 18, 2020, at 11:25, Łukasz Langa wrote:
> the beta 1 release of Python 3.9.0 planned for today is as of now blocked on
> three issues marked as "release blocker":
>
> - https://bugs.python.org/issue26317
-> Resolved by a revert
--
Ne
https://discuss.python.org/t/python-3-7-7-is-now-available/3682
https://www.python.org/downloads/release/python-377/
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email
Details here:
https://discuss.python.org/t/python-3-7-7rc1-is-now-available-for-testing/3638
https://www.python.org/downloads/release/python-377rc1/
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list -- python-committers
https://discuss.python.org/t/3-7-7-schedule-accelerated-cutoff-now-2020-03-02/3511
--
Ned Deily
n...@python.org -- []
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le
ot cause issue: urlparse's API is not suited for parsing both
strictly RFC-compliant URLs (which are clearly not well-understood) *and*
today's schemeless URLs as have evolved over the years to become the most
commonly encountered form of URL. Users want and need both. The merged change
m
e87ba86b082fa1c4a77f ). Senthil, please go ahead and do so
for the 3.7 branch. Thanks!
While it's not my call, I think we should also revert for 3.8.2.
For 3.9.0, I recommend we reconsider this change (temporarily reverting it) and
consider whether an API change to accommodate the vario
s.
git checkout v3.3.7 # for final 3.3 release (in detached HEAD mode)
git checkout v3.3.7 -b v3.3.7 # to also create a local branch
git checkout 3.3 -b 3.3 # for the final state of the 3.3 branch
https://git-scm.com/book/en/v2/Git-Basics-Tagging
--
Ned Deily
n...@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
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
.
--
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
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
/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
][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
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
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/
--
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
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
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
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
>
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 --
/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
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
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
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
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
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/
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
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
#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
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 -- []
_
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
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/
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
/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/
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
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
/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
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
-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
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.
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
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
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
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
, 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
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...
://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
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
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
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 -- []
__
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
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
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...
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!
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
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
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
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 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
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 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
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 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)
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
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!
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
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
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
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
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/
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 -- []
___
/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
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/
--
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/
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
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
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
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
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!
-
1 - 100 of 231 matches
Mail list logo
