python-devel August 2016

python-devel@lists.fedoraproject.org

22 participants
25 discussions

python34 for EPEL6
by Orion Poplawski 25 Aug '16

25 Aug '16

I have no idea if there is any interest in this or not. I managed to get the EPEL7 python34 package to build on EL6 with a few modifications. Is there any interest in supporting this? -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion(a)nwra.com Boulder, CO 80301 http://www.nwra.com

6 9

unscribe
by Brad Bell 22 Aug '16

22 Aug '16

How does one unsubscribe from this list ?

2 1

.egg-link?
by Igor Gnatenko 22 Aug '16

22 Aug '16

$ cat /usr/lib/python3.5/site-packages/Flask.egg-link /builddir/build/BUILD/python3-python-flask-0.10.1-9.fc25 . I think we should exclude all egg-links from distribution.. Also question comes what we should do from RPM generator. Neal proposed for now to just skip it[0].. [0] https://github.com/rpm-software-management/rpm/pull/80 -- -Igor Gnatenko

3 3

[Errno -3] Temporary failure in name resolution
by Germano Massullo 19 Aug '16

19 Aug '16

Hi everybody! I have just submitted to Fedora repositories, a new package called python-gfm. I was running the first build on Koji, when I got some errors related to python-markdown2, so I would like to ask you if you have any idea about... I am getting error <<Download error on https://pypi.python.org/simple/markdown/: [Errno -3] Temporary failure in name resolution -- Some packages may not be found!>> python-gfm spec file: http://pkgs.fedoraproject.org/cgit/rpms/python-gfm.git/tree/python-gfm.spec Build error log: https://kojipkgs.fedoraproject.org//work/tasks/3969/15283969/build.log Thank you very much! Have a nice day

3 3

Rebasing Python, deleting patches
by Tomas Orsava 17 Aug '16

17 Aug '16

Hi, I'm currently rebasing Python to version 3.5.2 for Fedora 25. As many of the existing patches are no longer necessary I needed to delete or disable them. I looked through the git history of python and python3 packages, and there isn't a clear consensus on which method is preferred. While python3 package so far only has patches deleted, python package had many patches that were just disabled/commented out, but not deleted. I decided deleting no longer useful patches is the better option, not only because it was a more prevalent method in the past, but also because it keeps the spec file clean for the years to come. No data is actually lost as it remains in git history. Tomas

3 2

Update python-django EPEL7
by Germano Massullo 16 Aug '16

16 Aug '16

Hello, I would like to ask if it is possible to update python-django for EPEL7 to, for example, 1.8 version. I am actually going to fill a Review Request for python-django-netjsongraph[1], and among its requirements, there is python-django-rest-framework that cannot actually be packaged for EPEL7 due python-django actual version Thank you [1]: https://github.com/interop-dev/django-netjsongraph

5 4

Python 3.5.2
by Tomas Orsava 16 Aug '16

16 Aug '16

Hi! I'm happy to inform you that I've rebased Python 3 in Fedora rawhide to a new version 3.5.2 up from 3.5.1. The official build has just finished [0], and should show up in rawhide repos in the upcoming days. I invite everyone to try it out, if all goes well I'll push the update to Fedora 25 as well. [0] http://koji.fedoraproject.org/koji/taskinfo?taskID=15274894 Good day to all, Tomas Orsava

1 0

[Python-SIG] Self-Introduction: Tim Orling
by Tim Orling 15 Aug '16

15 Aug '16

Greetings, I recently became a co-maintainer for pystatgrab [1] and am a contributor to upstream [2]. I am a co-founder and co-maintainer of the meta-python [3] and meta-maker [4] layers for OpenEmbedded. I am also a contributor to IronPython [5] and RobotFramework [6]. In my professional life, I work for the Intel Open Technology Center on the Yocto Project, which depends heavily on Python for its tools and infrastructure. [1] https://admin.fedoraproject.org/pkgdb/package/rpms/pystatgrab/ [2] https://github.com/i-scream/pystatgrab/graphs/contributors [3] https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ [4] https://layers.openembedded.org/layerindex/branch/master/layer/meta-maker/ [5] https://github.com/orgs/IronLanguages/people [6] https://github.com/robotframework/robotframework/graphs/contributors

5 12

Python 3.6 and Python-SIG
by Charalampos Stratakis 15 Aug '16

15 Aug '16

Hello everyone. A Change proposal has been created for Fedora 26 in order to rebase Python 3 stack to 3.6. You can view the change here [0]. Reviews, questions etc are welcome. For people who want to do some early testing you can install it by enabling my copr repo: dnf copr enable cstratak/python-3.6 Please be aware that this is an alpha version and the copr builds so far are experimental (some patches need reviewing, some package changes are not documented etc), so builds might disappear, updated, downgraded etc. As an added note, Python-SIG wiki page is (slowly) being updated [1]. Feel free to add your own knowledge, notes and so on. [0] https://fedoraproject.org/wiki/Changes/Python3.6 [1] https://fedoraproject.org/wiki/SIGs/Python Regards, Charalampos Stratakis Associate Software Engineer Python Maintenance Team, Red Hat

1 0

Python 3 porting: 50% done in Rawhide 🎉
by Petr Viktorin 12 Aug '16

12 Aug '16

Hello, As of now, http://fedora.portingdb.xyz shows that we are 50% done porting Fedora packages to Python 3. This is a big magic milestone; if you're looking for a reason to celebrate, this is it! :) Meanwhile, let me talk about what the number means and what the next steps are. 50% packages are "done" in Rawhide. "Done" is defined as either "Released"/"green" (packages that are either py3-only, or have py3 and py2 variants packaged), or "Dropped"/"gray" (package won't be ported, but there's a py3-compatible alternative packaged in Fedora -- for example: "python" is dropped because "python3" is available; "python-numeric" is dropped in favor of "numpy" even though the API s are different). The classification of "green" packages is mostly automatic, and it's not perfect -- for example, python-twisted is green even though not all of the submodules are ported yet, and nothing checks if the packaged py3 versions actually works. For cases when there's a problem with the automatic process, manual overrides or notes can be put in [fedora-update.yaml]. Portingdb tracks Rawhide; Fedora 25 is currently missing about 4 packages to get to 50%. It might very well get to 50% before the release. Now, what's next? I can't speak for everyone involved, but at Red Hat's python-maint team, we'll tone down the focus on getting as many packages ported as possible. This led to us picking the low-hanging fruit, which is better left to people that are just getting started. We'll be around to answer questions, provide hints, and otherwise help others get the badges instead of stealing them for ourselves :) Instead, we should shift our focus from porting specfiles to upstream projects. At this point, if some software is easy to port it was probably ported already; what we're left with are either tough nuts to crack or projects with few people relative to the codebase size. Some projects that come to mind that could use attention are GTK, Mercurial, Samba, wxPython, PySide, Koji & Fedora infra, Ansible. I don't know yet what our priorities should be here, but that's the general direction. But even if it won't be *our* focus, RPM porting is still open – you can [contribute] toward the remaining 50%! Badges are waiting :) [fedora-update.yaml] https://github.com/fedora-python/portingdb/blob/master/data/fedora-update.y… [contribute] http://fedora.portingdb.xyz/howto/ -- Petr Viktorin

4 5

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

python-devel August 2016