This issue tracks the release note for the following F26 Change:
https://fedoraproject.org/wiki/Changes/Python3.6
If you want to write this release note, then:
Note that sometimes, the contact people are unresponsive. Try to do your best, but if nobody gets back to you, it's not the end of the world.
Once you're done with the above, make sure to either commit the relnote to an appropriate section of the Release Notes book, or, if you're not familiar with Git, DocBook, or whatever else, just add it to this issue as a comment and let pbokoc[1] know that you're done with this one and you'd like the note included. Be sure to do this at least one day before the final release (so the limit is July 10 according to the current schedule). Also make sure to do this even for relnotes that haven't been checked by the change owner.
[0] You can do that by asking the change owner listed on the wiki page; alternatively you can infer it by checking the tracker bug (linked in Wiki) in Bugzilla and looking at its status; see bug comments for details. Ask someone on the mailing list or on IRC if you're not sure. [1] In #fedora-docs on FreeNode (UTC+1 timezone, online mostly during the day on weekdays), or pbokoc@redhat.com if you can't get a hold of me on IRC.
@torsava @pviktori @churchyard @mcyprian @lbalhar @Dkrejci @cstratak could you all provide us with a brief overview of the changes a user should expect and any cautions from this change. Please also provide a pointer to the upstream release notes for users wishing to fully explore the change.
Will that do? https://fedoramagazine.org/python-3-6-0-fedora-26/
@churchyard it can. If any of you all have time to distill that down further into this ticket that would be a huge help as we are a bit short of people on this end.
Metadata Update from @bex: - Issue tagged with: stubbed
How long should that be? Could you please point me to a similar release notes in the past? i don't remember us writing those for 3.5.
@churchyard Yeah, we usually cover that on our end using upstream notes, e.g.: https://docs.fedoraproject.org/en-US/Fedora/24/html/Release_Notes/sect-Release_Notes-Changes_for_Developers.html#sect-Development . Bex was asking because this time we're in a bit of a rush and we can use all the help we can get. Plus, you're more familiar with the subject matter than anyone from docs is.
If you want to go through the upstream notes and pick a few items you consider more important than others (stuff that should be listed in Fedora's relnotes), it would definitely help us. If you can't/don't want to, I'll go through them later this week and pick something myself.
Metadata Update from @pbokoc: - Issue assigned to pbokoc
Hello. I believe the major highlights from https://fedoramagazine.org/python-3-6-0-fedora-26/ should be sufficient, as it served the same purpose.
On it.
Python 3.6 will be the default Python 3 stack in Fedora 26. This is an upgrade from 3.5 which was included in Fedora 25. All packages which depend on Python 3 must be rebuilt. User-written Python 3 scripts and applications may require a small amount of porting; however, Python 3.5 is forward compatible with Python 3.6 for the most part.
Notable new features include:
f"This will be evaluated to foo's value: {foo}"
secrets
1_000_000
open()
pathlib.Path
pathlib.PurePath
For more detailed information see our Fedora Magazine article or the upstream release notes. Note the Porting to Python 3.6 section, which lists important information for developers who need to port their Python 3.5 applications.
Perfect, thanks! I added your text to the f26 branch, the commit is here: https://pagure.io/release-notes/c/c60448a8173ea0e4ee4009d9793f132543d6d621?branch=f26
I'll close the issue since I used the above text almost verbatim so it doesn't need to be checked.
Metadata Update from @pbokoc: - Issue untagged with: stubbed - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.