Michal Cyprian wrote:
there is a long-standing problem that `sudo pip install` cannot be safely used
in Fedora. Many users don't know about this and break python packages on theirs
systems. Packages installed using this command can conflict and overwrite
Python rpm packages.
This is a major p
Miro Hrončok пишет:
> On 27.2.2015 21:06, Miro Hrončok wrote:
> Oh it seems only in the latest revision someone took the courtesy of
> translating it all to Russian.
That text is machine-translated and poorly at that.
--
Zart
___
python-devel mailing l
Thomas Spura wrote:
On Tue, Aug 14, 2012 at 9:42 AM, Nick Coghlan 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 sit
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
Bohuslav Kabrda wrote:
Thanks a lot... I didn't know that all the modules get imported during
install... I guess moving that code somewhere to the archive class will do fine.
Your own setup.py contains explicit import from pyp2rpmlib, thus
monkeypatching happens even before setuptools/distri
Bohuslav Kabrda wrote:
line 154, in unpack_zipfile
data = z.read(info.filename)
File "/usr/lib64/python2.7/zipfile.py", line 869, in read
return self.open(name, "r", pwd).read()
File "/usr/lib64/python2.7/zipfile.py", line 683, in __init__
raise RuntimeError, "That compressio
Erik Blankinship wrote:
> Unfortunately, none of the gfx are transfered over. However, if I
> modify my setup.py as follows:
>
> from setuptools import find_packages
>
> pkgs = find_packages( )
>
> setup( name='SunnyApp',
> ...
> data_fil
