FWIW an old idea I had for revamping how we maintain Python packages
can
be seen here:
http://lists.fedoraproject.org/pipermail/python-devel/2010-March/000213.html
with some further ideas here:
https://fedoraproject.org/wiki/DaveMalcolm/PythonIdeas
(you can tell that page is old, it still mentions Unladen Swallow and
Pynie...)
I still like the basic idea: introduce a tool that captures the info
on
python runtimes for a given release in one place, and use it
programmatically within specfiles to avoid copy&paste. Although the
proposal isn't complete (how to handle exclusions?), I'm still fond
of
it.
Personally, I like the idea. As you say, there are still some issues, but I
guess we could solve those easily.
There is IMHO one downside of this approach - the complexity. I fear that
rpm-pyconfig can be easily taken to such extremes, that we will end up with
completely unintelligible specfiles.
As for supporting more runtimes (e.g. Pypy), I would be very careful about
that, as it might get us overloaded by tons of issues of different packages
with different runtimes.
Here is a wild idea: Would it be possible to create a common site-packages
directory for all runtimes? I don't know much about how different runtimes
handle bytecode generated by another runtime etc, but it may be worth looking
into, if we want to support more runtimes with our packages.
While this is pretty nice idea it's not feasible unless all runtimes
support http://www.python.org/dev/peps/pep-3147/ and
http://www.python.org/dev/peps/pep-3149/ which will require some
backporting in 2.x series.
--
Zart
_______________________________________________
python-devel mailing list
python-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/python-devel
