Python 3.8.0b1 is now available for testing
by Miro Hrončok
Fedora 30: https://bodhi.fedoraproject.org/updates/FEDORA-2019-204584be85
Fedora 29: https://bodhi.fedoraproject.org/updates/FEDORA-2019-e77f7dbb32
Copr with the "python3" package updated (to use in mock):
https://copr.fedorainfracloud.org/coprs/g/python/python3.8/
-------- Forwarded Message --------
Subject: [Python-Dev] [RELEASE] Python 3.8.0b1 is now available for testing
Date: Wed, 5 Jun 2019 00:44:04 +0200
From: Łukasz Langa <lukasz(a)langa.pl>
To: Python Committers <python-committers(a)python.org>, Python-Dev
<python-dev(a)python.org>, python-list(a)python.org, python-announce(a)python.org
The time has come for Python 3.8.0b1:
https://www.python.org/downloads/release/python-380b1/
This release is the first 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.0b2, currently scheduled
for 2019-07-01.
Call to action
We *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
<https://bugs.python.org> 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.
A new challenger has appeared!
With the release of Python 3.8.0b1, development started on Python 3.9. The
“master” branch in the cpython repository now tracks development of 3.9 while
Python 3.8 received its own branch, called simply “3.8”.
Acknowledgments
As you might expect, creating new branches triggers a lot of changes in
configuration for all sorts of tooling that we’re using. Additionally, the
inevitable deadline for new features caused a flurry of activity that tested the
buildbots to the max. The revert hammer got used more than once.
I would not be able to make this release available alone. Many thanks to the
fearless duo of Pablo Galindo Salgado and Victor Stinner for spending tens of
hours during the past week working on getting the buildbots green for release.
Seriously, that took a lot of effort. We are all so lucky to have you both.
Thanks to Andrew Svetlov for his swift fixes to asyncio and to Yury Selivanov
for code reviews, even when jetlagged. Thanks to Julien Palard for untangling
the documentation configs. Thank you to Zachary Ware for help with buildbot and
CI configuration. Thanks to Mariatta for helping with the bots. Thank you to
Steve Dower for delivering the Windows installers.
Most importantly though, huge thanks to Ned Deily who not only helped me
understand the scope of this special release but also did some of the grunt work
involved.
Last but not least, thanks to you for making this release more meaty than I
expected. There’s plenty of super exciting changes in there. Just take a look at
“What’s New <https://docs.python.org/3.8/whatsnew/3.8.html>”!
One more thing
Hey, fellow Core Developer, Beta 2 is in four weeks. If your important new
feature got reverted last minute, or you decided not to merge due to inadequate
time, I have a one time offer for you (restrictions apply). If you:
* find a second core developer champion for your change; *and*
* in tandem you finish your change complete with tests and documentation
before Beta 2
then I will let it in. I’m asking for a champion because it’s too late now for
changes with hasty design or code review. And as I said, restrictions apply. For
instance, at this point changes to existing APIs are unlikely to be accepted.
Don’t start new work with 3.8 in mind. 3.9 is going to come sooner than you think!
- Ł
4 years, 10 months
Re: I found 2 problems on remove python2-foo packages
by Neal Gompa
On Tue, Jun 4, 2019 at 3:26 AM Nico Kadel-Garcia <nkadel(a)gmail.com> wrote:
>
> On Mon, Jun 3, 2019 at 10:51 AM Sérgio Basto <sergio(a)serjux.com> wrote:
> >
> > Hi,
> > These removed python2 packages are breaking upgrade path
> >
> > 1- when you remove python2-foo , you should add to main package
> > Obsoletes: python2-foo
>
> If I may suggest, *absolutely not*. "Obsoletes: python2-foo"
> specifically means that it includes and provides "python2-foo"
> functionality, and "python3-foo" packages *do not* provide this. There
> are a very few tools that put things in "/usr/bin" for typical use,
> such as the "rpm" package itself which might benefit from such
> options. But I think it's quite dangerous to replace them willy-nilly
> due to compatibility for old packages which would have their
> requirements replaced with something quite incompatible without
> notification.
>
I think you misunderstand here. Obsoletes does not specifically
indicate it is equivalent. It is saying that you're replacing it. You
will still get a broken dep chain if something Requires something that
was obsoleted.
It is absolutely the correct strategy to do Obsoletes (without Provides) here.
--
真実はいつも一つ！/ Always, there's only one truth!
4 years, 10 months
Re: I found 2 problems on remove python2-foo packages
by Sérgio Basto
On Tue, 2019-06-04 at 03:25 -0400, Nico Kadel-Garcia wrote:
> If I may suggest, *absolutely not*. "Obsoletes: python2-foo"
> specifically means that it includes and provides "python2-foo"
> functionality,
No , on update just force remove of python2-foo , doesn't provide it .
instead dnf broken dep, python2-foo requires foo=n when foo=n+1 .
I remembered and as Leigh wrote : "The python2-foo removed packages be
added to the fedora-obsoletes package."
but not all python2-foo packages are in fedora-obsoletes and we also
may not install fedora-obsoletes package ...
Best regards,
--
Sérgio M. B.
4 years, 10 months
I found 2 problems on remove python2-foo packages
by Sérgio Basto
Hi,
These removed python2 packages are breaking upgrade path
1- when you remove python2-foo , you should add to main package
Obsoletes: python2-foo
2- IMHO you should just remove python2-foo only on latest branches,
please don't forget epel7 case, so please add something like :
%if 0%{?fedora} >= 30
%endif
Thanks,
--
Sérgio M. B.
4 years, 10 months
Introduction
by Marcel Plch
Hello,
I am Marcel, on most social networks I use the nickname 'Dormouse759'.
(a translation of my surname plus some numbers, very creative, isn't
it?)
I work for Red Hat in the Python Maintenance team and already
contribute to some bugfixes here on Fedora, though most of my work is
on RHEL currently. I also contribute to upstream, maintain the package
python-libsass and co-maintain cronie, crontabs and at packages.
Mostly I contribute to cpython upstream, fix some well hidden bugs in
larger Python projects or its bindings (Cython, eventlet, gdb etc.)
There also are some projects (mostly planned yet) I have in copr. I
would like to expand these and eventually move them to Fedora to make
my (and hopefully others') workflow easier.
Except for Python, I work also on some C projects.
--
Marcel Plch
4 years, 10 months
