Renaming Feature for F19 [was: Re: Switching to Python 3]
by Thomas Spura
On Tue, Aug 14, 2012 at 9:42 AM, Nick Coghlan <ncoghlan(a)redhat.com> wrote:
> However, I think it's enough to place a clear upper limit on the number
> of runtimes to be supported (where 'x' is the relevant minor version
> packaged in the Fedora repos): CPython 2.x, PyPy 1.x, Python 3.x (with
> shared site-packages)
I don't know if pypy1-foo makes sense or how they want to support
python2 and python3 at the same time. But I'm all for pypy1-foo to be
on the save side...
One thing, that comes to my mind:
Should it be python2-foo or cpython2-foo?
Otherwise, I went ahead and created a feature page:
https://fedoraproject.org/wiki/Features/PythonNamingDependingOnImplementa...
Feel free to add yourself to the "owner" list and change it, when
there is something missing.
I would propose, that we agree to a IRC meeting, where we can discuss
possible differences or do you think anything is sorted out now and
the feature is "sane" for anyone?
Greetings,
Tom
11 years
Orphaning python-migrate in devel
by Toshio Kuratomi
Just a heads up that I've just orphaned python-migrate in devel. Despite
playing around with it many times, I've never actually gotten to the point
where I could use it in the code I'm writing. Ralph Bean has also just
gotten python-alembic reviewed for Fedora. From a look at it, alembic
should be able to serve the same use cases as python-migrate and has some
nice additional features as well.
If someone wants to take over migrate feel free -- I'd be happy to release
the other branches to your care as well. If not, it will eventually be
retired in the once-a-release retirement of orphaned packages.
-Toshio
11 years, 1 month
Introduction and a query
by Amit Saha
Hi all,
I am Amit and just joined the mailing list here to keep track of
Python developments on Fedora.
I had a rather subjective question and I may have missed any
documentation on the same. Python packages are easily installed via
'pip-python'. For Python packages which are not yet packaged for
Fedora, is it a great value addition if I would pick it up and package
it? Or, should I consider it only if I or someone else needs it to be
there in the Fedora repositories for a reason - for example, I wanted
to include 'picloud' client library in the Scientific Spin and hence
decided to package it [1].
Does the SIG consider an interest in packaging any useful Python
module for Fedora as a value addition to the Fedora community? What
determines its acceptance, other than the package being correctly
built/conforming to the guidelines?
[1] https://bugzilla.redhat.com/show_bug.cgi?id=799810
Thanks,
Amit
--
http://echorand.me
11 years, 1 month
Switching to Python 3
by Bohuslav Kabrda
Hi,
I'd like to start a discussion about the release where we should switch to Python 3. As I have learned recently, Ubuntu 12.10 will have Python 3 as default [1], which makes me a sad panda :(
We always take pride in being close to upstream and having the bleeding edge. Python 3 is stable and more and more libraries support it. So I'd like to propose an idea to switch to Python 3 for Fedora 19.
Please note, that I don't want to start a flamewar with this, but a serious discussion. I want to know what python SIG thinks about taking this step before taking it to wider public on fedora-devel.
--
Regards,
Bohuslav "Slavek" Kabrda.
[1] https://wiki.ubuntu.com/QuantalQuetzal/TechnicalOverview/Alpha3#Python_3.0
11 years, 1 month