Self Introduction: Arvind
by Arvind Chembarpu
Hi everyone,
I'm Arvind - a 20yr old Computer Science student from Mysore, India. I started my coding journey with python, and have been hooked ever since.
I specialize mainly in fullstack web development, and try my best to contribute to open-source projects (https://github.com/arvindch). You can find me on IRC - @arvindch / @achembar.
I'm excited to be working with the QA Team at Fedora, as an Intern. Redhat has always been an inspiration to me, ever since I started my journey with Linux/GNU almost a decade ago! I'm very interested in testing, and contributing to Fedora, in whatever way I can. So, I identified the Python SIG as good starting point for my interests.
From what I understood on [https://fedoraproject.org/wiki/SIGs/Python], an Intro email is the way to request permission to join the Python SIG. I've subscribed to the python-sig and python-devel mailing lists, as well. Let me know if I've missed a step.
Cheers!
Arvind
[achembar(a)redhat.com / arvindch(a)gmail.com]
7 years, 2 months
Request for Review: Python marketing brochure
by Justin W. Flory
Hello all,
Brian (bprofitt / bkp) recently helped finish the final proposed version
of the brochure we plan to use in the field for quick information about
Fedora + Python.
If some Pythonistas could help review the brochures and make sure the
content checks out and sounds good, your help would be appreciated!
You can find the latest copies of the brochure in this ticket.
https://fedorahosted.org/marketing-team/ticket/219
To help prevent communications from being lost in cross-posted mailing
lists, if anyone who is able could give a +1 / -1 in the ticket, that
would be appreciated! Thanks all.
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7 years, 2 months
python 2.7.11
by Orion Poplawski
Is there some reason that python in F23 hasn't been updated to 2.7.11 (from
2.7.10)?
--
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
7 years, 2 months
Package Sprawl or Why I lost Motivation for Python34 in RHEL 7
by Avram Lubkin
So, a package I help maintain, python-dns is now provided by Red Hat. So I
thought, "OK, I'll still build the python34 package to help in that
effort". But the problem with that is, per the EPEL 7 in Python 3 Plan
Draft (1), if Red Hat provides the package, the SRPM can't use the same
name. I can see the merit there. The problem is that in Fedora, a SRPM name
needs to match the git repo name. So, yes, I could ask for a python3-dns
package to be setup, but that creates two problems. The first, keeping the
EPEL-only repo in sync with the main repo. The second, Differentiating
between the python3 package for Fedora which is in the python-dns git repo
and the python3 package for EPEL which, according to the guideline, would
be in python3-dns.
Ideally, I'd be able to maintain everything in the main git repo and use
one spec file cloned from master. That's not too difficult except the
Fedora build system won't build a package if it can't find the package
(based on the SRPM name) in the database.
I don't see a clean solution which makes me very hesitant to preemptively
put out python34-dns for EPEL7. Which is part of the whole problem with
python34 on EL7, there are no packages. If you build it, they will come,
otherwise everyone stands around complaining it's not built.
Am I missing something?
Avram
1:
https://fedoraproject.org/wiki/User:Bkabrda/EPEL7_Python3#Packaging_Paral...
7 years, 2 months
Inconsistencies in the Fedora Packaging Guidelines for Python
by Tomas Orsava
Hi,
according to the "Fedora Packaging Guidelines for Python" [0] the "Example common spec file" [1] contained in those very same guidelines is wrong.
Specifically, the section "Naming" [2] in the guidelines says the following:
(1) "Both python 2 and python 3 variants must provide symlinks with a '-X' and '-X.Y' suffix (python runtime major version, or python runtime major.minor version), unless upstream already provides appropriately versioned executables without the dash."
(2) "The unversioned executable must be the python2 version."
(3) "For example, the python3 version of "coverage" must ship executables /usr/bin/coverage-3 and /usr/bin/coverage-3.4 (assuming python3 is currently version 3.4), while the python2 version must provide /usr/bin/coverage, /usr/bin/coverage-2 and /usr/bin/coverage-2.7 (assuming python2 version 2.7)."
So given that, the "Example common spec file" [1] has the following problems:
* The unversioned executable ('%{_bindir}/sample-exec') is provided by the python3- subpackage instead of the python2- subpackage.
* In the %install section, the order of execution of the %py2_install and %py3_install macros is wrong, since it leads to python3- subpackage providing the unversioned executable. The comment in the section should be modified accordingly as well.
* Neither python2- nor python3- subpackages provide symlinks to the '-X' suffix, i.e. 'sample-exec-2' and 'sample-exec-3'
[0] https://fedoraproject.org/wiki/Packagingython
[1] https://fedoraproject.org/wiki/Packagingython#Example_common_spec_file
[2] https://fedoraproject.org/wiki/Packagingython#Naming
Thank you for your time,
Tomas Orsava
7 years, 2 months
Re: [Marketing] Help Getting Started - Python Talking Points and
Meetings
by Justin W. Flory
Hi James,
On 03/18/2016 03:41 PM, James Bishop wrote:
> Hi Justin
>
> The biggest question I have right now is whether I need to be a part of
> the marketing group to log in to the other sites. I have an FAS
> account, and the CLA has been signed, but when I try to sign on to the
> TRAC, I get a "you are not allowed here" message, and the wiki tells me
> that my login info is bad.
Yes, the best place to add some more info would definitely be the Trac.
The reason why you are unable to log in is because there are some
temporary limitations added to the wiki and all Trac instances to block
a recent bout with spambots attacking both services. You should stop by
in #fedora-admin and ping either puiterwijk or nirik to add your FAS
account to the antispam-ack group. This limitation is actually due to be
lifted sometime today, but if you are unable to log in still, please let
the folks know there and they can help get you logged in!
> As for what I <3 about Python in Fedora, I would say that it comes down
> to the fact that the packages I need are in the repos, so I can manage
> everything with one package manager, and the ease of transition to RHEL
> instances. That said, I didn't really choose Fedora as a Python
> developer, but as someone who appreciates free software and Fedora's
> stance on it.
>
That kind of feedback is definitely good to hear. Whatever your
experience or profession is, adding that in somewhere for consideration
should definitely happen. Let's see if we can get your Trac permissions
resolved and then add that to the ticket.
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7 years, 2 months
Putting the spotlight on Python
by Justin W. Flory
Hi Python SIG!
Over in Marketing, we've been having some discussion about creating
talking points for our Ambassadors to help show people how Fedora and
Python go great together.
https://fedorahosted.org/marketing-team/ticket/219
We've got a few ideas together so far, but we were wanting to get some
more opinions and thoughts from you all on this. Some of our ideas were
seeing if you all were interesting in putting on another porting vFAD
like what happened a few months ago, and then we help put a little more
press and marketing before and after the event too. In addition to
helping actually move more Python2 packages to Python3, it could also be
a great way to show people how Fedora is current and helping assist with
the migration. But we wanted to see if this was something feasible to
you all.
Finally, we are also trying to compile a list of talking points
(generally speaking) for Python, and there is currently a draft for
these things on the wiki. If you all could look over these and add your
input, it would be well-appreciated!
https://fedoraproject.org/wiki/Objectives/Fedora_Marketing_Python
Thanks all, looking forward to hear your responses and ideas.
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7 years, 2 months
Turning on automated bugs & scratch builds for pip & virtualenv?
by Nick Coghlan
The pkgdb currently has the ability to automatically monitor for new
upstream releases and attempt scratch builds in Koji when they're
published. "rebase-helper" was recently integrated into that so the
automated rebuilds are more likely to succeed.
Another new feature recently added was pinging all of the package
watchers every time Anitya detected a new build, but automatic BZ
filing and scratch builds were disabled :)
Would it be worth trying turning that on for these packages? I'd also
be happy to finally start down the path towards co-maintainership if
that would tip the answer towards "Yes" :)
Cheers,
Nick.
--
Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia
7 years, 2 months
