python-devel August 2015

python-devel@lists.fedoraproject.org

9 participants
6 discussions

Python 3 additions to the Fedora 23 release notes?
by Nick Coghlan 30 Aug '15

30 Aug '15

Something Joe Brockmeier mentioned in his Fedora Marketing talk at Flock last week was the need for development teams to be active in providing content for the release announcements. With the Fedora 23 Alpha coming out last week, I looked at the Release Notes to see if there was anything about the "Python 3 as default" change, but didn't see anything. Was there something there and I just missed it, or does something need to be written up and passed to the folks responsible for creating the release notes? Regards, Nick. -- Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia

3 3

Packaging sphinx docs
by Robert Kuska 27 Aug '15

27 Aug '15

While figuring out how to proceed with development of pyp2rpm I've realized that I have no idea how to properly package docs generated by sphinx for python module having both python2 and python3 subpackages, I've decided to go with the following pattern: If package foo has docs generated with sphinx: - add BuildRequires: python-sphinx - use sphinx (unversioned binary) to generate docs - package docs under python-foo-docs subpackage Apply same behavior for every module, even if module ships both Python2 and Python3 subpackage its docs will be generated only once and stored under python-foo-docs. (Assuming that docs are same for both python major versions.) What do you think? -- Robert Kuska {rkuska}

2 1

New Package: python-scandir
by Avram Lubkin 19 Aug '15

19 Aug '15

Just thought I'd let this list know python-scandir is now in the stable repos. The code itself has been accepted as an enhancement to the os module in Python 3.5, but the original independent module is great for older versions. I tend to use as an optional speedup when I am heavily using os.walk() or os.listdir(). The maintainer has been very responsive. https://github.com/benhoyt/scandir

1 0

matplotlib packaging
by Thomas Caswell 18 Aug '15

18 Aug '15

Hello all, I am one of the lead upstream developers of matplotlib. We are in the process gearing up for two major releases in the next few months. First we will be doing a 1.5 release which will be a new feature release and has a new external dependancy (https://github.com/matplotlib/cycler) which will need to be packaged. There is a version of cycler on pip and I plan to do a 1.0 release of cycler around/before the mpl1.5 release. Right after that we will be doing a 2.0 release that will have no new features, but will be changing many of the visual defaults. Is there anything we can do upstream to make your lives easier on the packaging side? Thomas Caswell

2 1

Fedora Badge for Python 3 Efforts
by Matej Stuchlik 04 Aug '15

04 Aug '15

Hey folks, in connection with the "Python 3 as the Default Implementation" change [0], we're giving out badges [1] for helping making Fedora speak Python 3. Therefore, if you have added Python 3 support to 3 or more packages since f20, or if you have made significant contributions towards the Change, please let rkuska, bkabrda or me know, and you'll get your badge. :) Matt [0] https://fedoraproject.org/wiki/Changes/Python_3_as_Default [1] https://badges.fedoraproject.org/badge/parselmouth

1 0

Python guidelines cleanup
by Jason L Tibbitts III 03 Aug '15

03 Aug '15

As many of you may be aware, FPC has been fielding several tickets surrounding python packaging lately, and the last one was a sizable reorganization that unfortunately was based on an older version of the guidelines. While merging it all together I just said screw it and just cleaned up the page like I've always wanted to do. I suggest anyone who hasn't lost sanity due to this whole guidelines revision process pile onto: https://fedorahosted.org/fpc/ticket/552#comment:4 Here's the contents of that comment to save you a click. OK, this was a lot of stuff, and the more I worked on it, the more annoyed I became. Plus the wiki kept eating my edits and I kept getting lost in the overhuge page. So, I've probably gone too far in cleaning up but I'll present what I have and if people yell at me then I'll try something less ambitious. There are now three pages: https://fedoraproject.org/wiki/User:Tibbs/PythonCleanup2 https://fedoraproject.org/wiki/Packaging:Python_F21 https://fedoraproject.org/wiki/User:Tibbs/PythonAppendix The first page incorporates the following changes: * Notes that these guidelines apply only to F22+ and EPEL7. Points at the 2nd page for old guidelines. * Includes the information about not retiring python-version-specific subpackages in stable releases. * Makes BuildRequires: section much more succinct. * Makes sure python2-foo provide is versioned, mentions %python_provide macro. * Makes the macro table collapsible and collapsed by default. * Remove EL6-specific cruft (it's in the old guidelines page). * Move the parts of the byte compilation section that nobody ever uses off to the Appendix page. * Make the single-rpm single-dir case the default. Move the entire multiple-dir case to the appendix. * Completely remove %with_python3 from the example spec. We want people to build for python3. People just paste this in without knowing why they would ever need it. If you're using the new macros you can't just conditionalize for EL6 anyway. This really makes the spec look nice. Macro-izing the summary and description would make it look even nicer once the description gets longer than a line. * Uses a generic "example" module as an example. Two different approved proposals changed it to two different things; I just punted. * Puts the example spec all together without a bunch of text and admons and whatnot in the middle. * Moves the 2to3 section to the appendix. * Simply refers to the eggs section. That whole part at the bottom was quite awkward and I don't think most people even looked down that far. * Loads and loads of typo fixes, grammar fixes, and cleanups. The current main guideline page is now a bit over half the length it was and on the page it's less because of the collapsed macro table. I find it to be far more readable, and the sample spec no longer turns my stomach. The old guidelines page is just as it was before writing up the new macros, except that I added a short explanatory section at the top. The appendix page conveniently holds things which we probably should document but pretty much nobody would actually want to read without some specific reason. Functionally I do not believe I have gone beyond anything upon which we voted but I wanted to toss this out there and see if anyone yells before I copy it into place. Been trying to get this done for three days now and I think I'm finally there. - J<

5 11

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

python-devel August 2015