Toshio Kuratomi wrote:
> On Sat, Feb 11, 2012 at 09:00:55AM -0500, Neal Becker wrote:
>>
>> I always try out packages first via easy_install or pip (after checking they
>> are not already available via yum).
>>
>> Yes, I could try things via virtualenv, but I'm just not in that habit - and
>> I
On Sat, 2012-02-11 at 13:52 +0100, Matej Cepl wrote:
> c) If we want to have as many Python packages packaged in RPMs (the
> terminology is going to kill me soon) do we have some pip2spec (in the
> same manner as there is cpan2spec)?
Reading this I wrote that: https://github.com/pypingou/pypi2sp
On Sat, Feb 11, 2012 at 09:00:55AM -0500, Neal Becker wrote:
>
> I always try out packages first via easy_install or pip (after checking they
> are
> not already available via yum).
>
> Yes, I could try things via virtualenv, but I'm just not in that habit - and
> I
> suspect many others are
On Sat, Feb 11, 2012 at 01:52:08PM +0100, Matej Cepl wrote:
> b) distutils v. setuptools conflict is just an unfortunate testimony
> of immature bad state of the Python upstream packaging, but it seems
> to me that generally Python world is moving towards setuptools.
> Shouldn't we follow the suite
fre 2012-02-10 klockan 11:38 -0500 skrev Neal Becker:
> 80 wrote:
> > Never use pip outside an isolated environment (use virtualenv)
> >
> > H.
>
> Really? This is the only answer?
Does it help if we add that virtualenv is really useful? You can use it
to install a completely new copy of an a
Matej Cepl wrote:
> On 10.2.2012 18:09, 80 wrote:
>> Python guidelines recommends that packagers installs python eggs using
>> distutils (python setup.py install as recommended in guidelines) while
>> pip use the same install method as easy_install (provided by
>> setuptools/distribute). The forme
On 10.2.2012 18:09, 80 wrote:
Python guidelines recommends that packagers installs python eggs using
distutils (python setup.py install as recommended in guidelines) while
pip use the same install method as easy_install (provided by
setuptools/distribute). The former one install egg metadata as a
On Fri, 10 Feb 2012 11:32:31 -0500
Neal Becker wrote:
> I've seen this repeatedly, with often very serious consequences (complete
> failure of update from f15->f16 for example).
Yeah... My answer to this was:
\o/ PACKAGE ALL THE THNGS !!! O//
So I got git-review included into Fedora, wh
Haïkel Guémar wrote:
> Le 10/02/2012 19:20, Neal Becker a écrit :
>>
>> Yes, but trying to be helpful to users is a fedora packaging/rpm issue.
>>
>
> Generally speaking, mixing RPM packages with development platform here> native packages is not doing a favor to our
> users.
> I agree that some
Le 10/02/2012 19:20, Neal Becker a écrit :
>
> Yes, but trying to be helpful to users is a fedora packaging/rpm issue.
>
Generally speaking, mixing RPM packages with native packages is not doing a favor to our
users.
I agree that some users may need more up-to-date modules, but isolated
environme
80 wrote:
> 2012/2/10 Neal Becker :
>>
>> Really? This is the only answer? Can't we tweek rpm/yum to accomodate this?
>> Does anyone understand what is causing it? Why would pip install the
>> egg-info differently than rpm?
>>
>> --
>> devel mailing list
>> devel@lists.fedoraproject.org
>> http
On Fri, Feb 10, 2012 at 11:38:20AM -0500, Neal Becker wrote:
> 80 wrote:
>
> > 2012/2/10 Neal Becker :
> >> I've seen this repeatedly, with often very serious consequences (complete
> >> failure of update from f15->f16 for example).
> >>
> >> Between packages installed via pip, and packages instal
2012/2/10 Neal Becker :
>
> Really? This is the only answer? Can't we tweek rpm/yum to accomodate this?
> Does anyone understand what is causing it? Why would pip install the egg-info
> differently than rpm?
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraprojec
80 wrote:
> 2012/2/10 Neal Becker :
>> I've seen this repeatedly, with often very serious consequences (complete
>> failure of update from f15->f16 for example).
>>
>> Between packages installed via pip, and packages installed via yum, some
>> packages seem to switch between
>>
>> e.g.,
>> numpy-1
On 2/10/12 11:32 AM, Neal Becker wrote:
I've seen this repeatedly, with often very serious consequences (complete
failure of update from f15->f16 for example).
Between packages installed via pip, and packages installed via yum, some
packages seem to switch between
e.g.,
numpy-1.6.1-py2.7.egg-in
2012/2/10 Neal Becker :
> I've seen this repeatedly, with often very serious consequences (complete
> failure of update from f15->f16 for example).
>
> Between packages installed via pip, and packages installed via yum, some
> packages seem to switch between
>
> e.g.,
> numpy-1.6.1-py2.7.egg-info
>
I've seen this repeatedly, with often very serious consequences (complete
failure of update from f15->f16 for example).
Between packages installed via pip, and packages installed via yum, some
packages seem to switch between
e.g.,
numpy-1.6.1-py2.7.egg-info
being installed as a file and the sa
17 matches
Mail list logo
