Thanks everyone who's been involved in the formulation and discussion of
PEP 438 "Transitioning to release-file hosting on PyPI". I have today
accepted the PEP and the first phase of implementation is now underway,
spearheaded by Donald Stufft.
In a related note, I welcome and thank the fourth adm
On May 18, 2013, at 8:51 PM, Donald Stufft wrote:
> On May 18, 2013, at 8:50 PM, Donald Stufft wrote:
>
>> Phase 1 of PEP 438 (http://www.python.org/dev/peps/pep-0438/) has begun.
>>
>> Deployed to production PyPI is:
>> - New packages default to pypi-explicit
>> - Old packages default to
On May 18, 2013, at 8:50 PM, Donald Stufft wrote:
> Phase 1 of PEP 438 (http://www.python.org/dev/peps/pep-0438/) has begun.
>
> Deployed to production PyPI is:
>- New packages default to pypi-explicit
>- Old packages default to pypi-scrape-crawl
>- Package Maintainers can select whi
Phase 1 of PEP 438 (http://www.python.org/dev/peps/pep-0438/) has begun.
Deployed to production PyPI is:
- New packages default to pypi-explicit
- Old packages default to pypi-scrape-crawl
- Package Maintainers can select which hosting mode to use
- Package Maintainers can control
Hi Tres,
Noah noticed some resource issues yesterday and killed an offending
process. That could have been the cause of the problem.
Richard
On 19 May 2013 07:10, Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 05/18/2013 03:16 PM, Donald Stufft wrote:
> >
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/18/2013 03:16 PM, Donald Stufft wrote:
>
> On May 17, 2013, at 6:29 PM, Tres Seaver
> wrote:
>
>> Both in the web interface and in registration / upload of releases.
>>
> Is this still happening to you?
This afternoon I was able to register
On May 17, 2013, at 6:29 PM, Tres Seaver wrote:
> Signed PGP part
> Both in the web interface and in registration / upload of releases.
>
>
> Tres.
> - --
> ===
> Tres Seaver +1 540-429-0999 tsea...@palladion.co
