+1
On Sun, Sep 4, 2016 at 7:02 AM, Steve Dower wrote:
> "add it to setuptools first, and then add things to distutils where we
> feel they're sufficiently stable to not need the benefit of the faster
> setuptools update cycle"
>
> I nominate this as the official policy
On Wed, Aug 24, 2016 at 12:06 AM, Nick Coghlan wrote:
> On 24 August 2016 at 02:46, Donald Stufft wrote:
> > Abstract
> >
> >
> > This PEP recommends deprecating, and ultimately removing, support for
> uploading
> > certain unused or under used
Hi Meradj,
Are you in the Python interpreter when you type that? If so, that's your
problem. You need to be at your normal command prompt. Open a new shell or
terminal and type that command first.
If you've already started Python and are in the interpreter, that would
indeed, give you a syntax
ry:https://test.pypi.org/legacy/
> username:
> password:
>
> For downloading it’d be something like test.pypi.org/simple/
>
>
> On Aug 1, 2016, at 6:39 PM, Anna Ravenscroft <annara...@gmail.com> wrote:
>
> So for testing, we direct testpypi (in the pypirc) to t
To be specific, update .pypirc like this:
[testpypi]
repository=https://test.pypi.org/
On Mon, Aug 1, 2016 at 3:39 PM, Anna Ravenscroft <annara...@gmail.com>
wrote:
> So for testing, we direct testpypi (in the pypirc) to test.pypi.org,
> right?
>
> On Mon, Aug 1, 2016 at 3:26
So for testing, we direct testpypi (in the pypirc) to test.pypi.org, right?
On Mon, Aug 1, 2016 at 3:26 PM, Donald Stufft wrote:
> Just an FYI, test.pypi.org is now active (this is the Warehouse instance
> backed by Test PyPI). Once https://github.com/pypa/warehouse/pull/1416
Great timing! Thanks for letting us know. (I've updated it in the upcoming
Nutshell.)
On Sat, Jul 30, 2016 at 8:17 PM, Donald Stufft wrote:
> Hey!
>
> The PSF was finally successful in purchasing pypi.org from the person who
> previously owned it. Previously discussions had
I find the whole discussion quite unnerving honestly.
pip install should do just that. notifying me if I have a version and an
upgrade is availalbe for *pip*, makes sense. doing anything *else* is
scary.
I expect --upgrade for upgrading things. THEN it should upgrade to the
latest version,
On Fri, Jun 10, 2016 at 2:53 PM, Glyph wrote:
> There might be a useful discussion buried in here about where official
> real-time _development_ discussion should go - but then, any weighty
> decisions should be discussed on the mailing list anyway to ensure that
>