On 12/19/2018 4:14 AM, Serhiy Storchaka wrote:
I propose to allow backporting bugfixes to 3.6 if
they do not need excessive work, but stop to fix 3.6 only bugs.
I think this would need a PEP.
After migrating to GitHab, backporting became less painful,
Before GitHub, we forward ported. For
On Dec 19, 2018, at 12:42, Serhiy Storchaka wrote:
> 19.12.18 19:01, Chris Barker - NOAA Federal via Python-Dev пише:
>>> [ extending 3.6 bugfix release phase? ]
>> [...]
> [...]
FYI, the discussion of this topic has proceeded to a conclusion on the
python-committers mailing list. TL;DR we are
19.12.18 19:01, Chris Barker - NOAA Federal via Python-Dev пише:
3.6 is the default Python in Ubuntu 18.04 LTS and RHEL 8. And due to several
important syntax features it can be a minimal required version for long time.
Which is a good argument for why we may not need longer term support
for 3
I’m all for extending the life of 3.6, it sure feels recent to me!
> 3.6 is the default Python in Ubuntu 18.04 LTS and RHEL 8. And due to several
> important syntax features it can be a minimal required version for long time.
Which is a good argument for why we may not need longer term support
f
Hi,
I am working in the Red Hat "Python-maint" team which is maintaining
Python 3.6 as the main Python interpreter in RHEL 8, which will likely
be supported for at least 10 years. And we have been supporting Python
2.7 in RHEL 7. So obviously, being able to benefit of the upstream
effort and infra
- Original Message -
> From: "Serhiy Storchaka"
> To: python-dev@python.org
> Cc: python-committ...@python.org
> Sent: Wednesday, December 19, 2018 10:14:41 AM
> Subject: Re: [Python-Dev] 3.7.2rc1 and 3.6.8rc1 cutoffs ahead, last 3.6.x
> bugfix release!
&g
04.12.18 10:42, Ned Deily пише:
A reminder: as previously announced, 3.6.8 is planned to be the last bugfix release of the 3.6
series. Python 3.6.0 was released on 2016-12-23, so by the time 3.6.8 is released, 3.6.x will have
been in bugfix mode almost exactly 2 years. When a new feature rele
https://discuss.python.org/t/3-7-2rc1-and-3-6-8rc1-cutoffs-ahead-last-3-6-x-bugfix-release/510/3?u=nad
OK, thanks to a lot of hard work by many of you, I think we are ready to
start the manufacturing of **3.7.2rc1** and **3.6.8rc1**.
For the **3.7 branch**, as usual feel free to continue to merg
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 to make
https://discuss.python.org/t/3-7-2rc1-and-3-6-8rc1-cutoffs-ahead-last-3-6-x-bugfix-release/510
We're reaching the end of the year and it's time for another pair of Python 3
maintenance releases, 3.7.2 and 3.6.8, before we ring out 2018. Since there
are still some open release blocker issues an
10 matches
Mail list logo
