Description of Problem:
In most situations the py file from the class lib aren't needed,
since the pyc/pyo are preferred when importing it.
It would be nice to include ONLY the pyc/pyo in the base python package
and add an adicional python-py package that included the .py files;
even further maybe the pyc/pyo files could be in separetad rpms.
Version-Release number of selected component (if applicable):
All version, filled against python2 because it's a major change
Won't do that. I'd rather drop the pyc files. We don't need huge amounts of new
emacs has emacs-el; what use are the 1.676 MB (in python 1.5.2, not checked
for 2.2 but I'm sure it's a bigger number) of python source code forthe
We are talking about an almost 20% reduction in an almost mandatory package,
with no functional loss.
Anyway, since when is a large number of packages a bad thing?
The Redhat Perl packages are moving in that direction...
I regularily use the .py files as reference/interface documentation.