I think the issue of Python distutils/setuptools is important. I posted a note to the Python Distutils SIG asking if there was any way I could do an RPN package (using bdist_rpm) with results going to my usual rpmbuild directory tree instead of being placed in the same directory tree as the sources and setup.py. I didn't get a response.
Meanwhile, everything seems to be eggs and easy_install that conflict with the overall system management aspects (and Linux Standards Base aspects) of RPM.
I think that any changes to fix the Python distutils/setuptools for RPMs will probably need to originate in the Fedora community.
Stan Klein
On Thu, March 18, 2010 8:00 am, David Malcolm dmalcolm@redhat.com wrote:
Message: 1 Date: Wed, 17 Mar 2010 15:36:35 -0400 From: David Malcolm dmalcolm@redhat.com Subject: Python SIG To: Fedora Python SIG python-devel@lists.fedoraproject.org Message-ID: 1268854595.30012.2147.camel@brick Content-Type: text/plain; charset="UTF-8"
I noticed that there's an effort to better organize the various Special Interest Groups in Fedora: https://fedorahosted.org/fedora-engineering-services/ticket/2
I noticed that although https://fedoraproject.org/wiki/SIGs/Python had "[[Category:Language-specific SIGs]]" we didn't have: "[[Category:SIGs]]" and so we weren't showing anywhere on that page.
I've fixed this, and the page is now at least showing on the list at the bottom of: https://fedoraproject.org/wiki/Category:SIGs
However, we're not in the hand-written list on that page, and I feel that we should be (hey, Ruby gets a mention, why can't we :) )
Any ideas what the summary info for the SIG should be? At the risk of plagiarism, Ruby's says: "A SIG for people who are interested in improving the state of Ruby in Fedora. This includes packaging Ruby libraries and applications, setting and improving standards for packaging them as RPM's and maintaining Ruby packages for Fedora."
and that might be a good first start, but I'd also include the runtime as well as libraries and applications - I don't want people to feel that the runtime is somehow sacrosanct (just more care required!).
How about this: "A SIG for people who are interested in Python on Fedora. This includes packaging and optimizing the various Python 2 and Python 3 runtimes (CPython, Jython), packaging libraries and applications, setting and improving standards for packaging them as RPM's and maintaining Python packages for Fedora." (somewhat copied from Ruby)
I think the various questions on the F-E-S ticket are good ones. I'm willing to do some work towards some of that ticket, but any help would be welcome.
Thoughts? Dave
Am 18.03.2010 15:39, schrieb Stanley A. Klein:
I think the issue of Python distutils/setuptools is important. I posted a note to the Python Distutils SIG asking if there was any way I could do an RPN package (using bdist_rpm) with results going to my usual rpmbuild directory tree instead of being placed in the same directory tree as the sources and setup.py. I didn't get a response.
Actually I read your mail but honestly I found it confusing / it was not clear to me what you're aiming at.
Meanwhile, everything seems to be eggs and easy_install that conflict with the overall system management aspects (and Linux Standards Base aspects) of RPM.
Can you elaborate this a bit more? What is 'everything'? Is it linked to Fedora or the fact that most projects publish eggs on their own?
I think that any changes to fix the Python distutils/setuptools for RPMs will probably need to originate in the Fedora community.
How do you think that should be fixed? What needs fixing? To me, the packaging situation in Python/Fedora is pretty good and I don't see much things that need fixing from Fedora point of view (besides setuptools/distribute).
fs
python-devel@lists.fedoraproject.org