Nathan Dunfield wrote:
Adding pip will require upgrading the version of setuptools that comes
with Sage, which is also a good thing since Sage is on 0.6.16 (which is
from 2011, I think) and the current version is 3.4.*
As of Sage 6.3.beta3, we're at setuptools 3.6 now, so that should no
longer
>
> [ ] Yes, make pip a standard part of Sage.
>
> [ ] No, pip does not belong in Sage.
>
Yes, pip should definitely be part of Sage. Independent of its potential
use dealing with spkgs, as the now standard Python package manager it's
something end users need. The very first thing I do w
On Wed, Apr 23, 2014 at 11:09 PM, mmarco wrote:
> Can it handle non-python packages?
No -- it is the standard package manager *for* Python.
> Or the idea is to use it only for python packages that need no compilation at
> all?
This question doesn't make sense to me, because many Python package
Can it handle non-python packages? Or the idea is to use it only for python
packages that need no compilation at all?
El jueves, 24 de abril de 2014 00:46:50 UTC+2, William escribió:
>
> Hi,
>
> There used to be a lot of confusion about which package manager /
> installer one should use with py
On Wednesday, April 23, 2014 6:46:50 PM UTC-4, William wrote:
>
> Hi,
>
> There used to be a lot of confusion about which package manager /
> installer one should use with python -- easy_install? setuptools?
> etc.
>
> Now the choice is clear: pip -- A tool for installing and managing
> Pyt
