move tarballs from SF to pypi

[tacaswell]

Received the following email, I assume several others did as well

We should sort out how to move the 1.2.0, 1.2.1, and 1.3.0 tarballs and nuke the master install that points at an SVN repo that I am not even sure still exists (and certainly is not up to date).

---

Hello Thomas.Caswell!

Please forgive me if this is the second (or third... I swear I tested it fully
this time!) copy you've received of this message, a bug has forced us to
resend the batch. Sorry for the extra noise D:

This is an automated message because you are listed as an owner or maintainer
of the following project on PyPI:

• matplotlib

Due to the acceptance of PEP 470, PyPI is going to remove the ability for a
project to host it's files somewhere other than on PyPI, but still have PyPI
instruct installers (such as pip) to go and fetch this file automatically.
PEP 470 removes this feature and any project relying on it will need to either
be moved to hosting on PyPI or, if you wish to continue to host it externally,
you'll need to host your own repository and instruct your users to add that
repository to their installer. To give you time to adjust, this change will not
happen for 3 months, but after that 3 month deadline has expired, unless you
act some or all of the files for the above projects will no longer be found by
automated installers.

If you wish, there is a script available at https://pypi.python.org/pypi/pep470
which can be used to automatically migrate any of the affected files for your
own projects to PyPI.

If you wish to continue to host your files yourself instead of uploading them
to PyPI, then you should follow the instructions at
https://packaging.python.org/en/latest/self_hosted_repository/.

If you have any questions about the migration, please first check the FAQ at
https://github.com/pypa/pep470/wiki/Frequently-Asked-Questions which will be
updated with any questions and answers that come up during the migration
process.

Here are all of the links that we've discovered for each project of yours which
are not currently hosted on PyPI:

matplotlib:
https://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib-1.2.0/matplotlib-1.2.0.tar.gz
https://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib-1.2.1/matplotlib-1.2.1.tar.gz
https://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib-1.3.0/matplotlib-1.3.0.tar.gz
https://svn.sourceforge.net/svnroot/matplotlib/trunk/matplotlib#egg=matplotlib-dev

Thanks for your time!
…

Donald Stufft
PyPI Administrator

[efiring]

Is there any point in keeping the old tarballs pip-installable? Or rather, is there enough to justify the fuss and the disk space?

[WeatherGod]

What should we do about Basemap?

On Thu, Sep 24, 2015 at 4:45 PM, Eric Firing notifications@github.com
wrote:

Is there any point in keeping the old tarballs pip-installable? Or rather,
is there enough to justify the fuss and the disk space?

—
Reply to this email directly or view it on GitHub
#5136 (comment)
.

[efiring]

On 2015/09/24 10:52 AM, Benjamin Root wrote:

What should we do about Basemap?

I would like to see Basemap migrated, but I don't know anything about
PyPi administrative operations.

Is there a fundamental problem because of its size?

[WeatherGod]

I think so, but I was going to inquire about that after the release of
matplotlib 1.5. Looks like I have to do that sooner rather than later. I
should probably contact Jeff Whitaker about transferring maintenance
control. I am also new to the whole PyPi administration stuff.

On Thu, Sep 24, 2015 at 5:02 PM, Eric Firing notifications@github.com
wrote:

On 2015/09/24 10:52 AM, Benjamin Root wrote:

What should we do about Basemap?

I would like to see Basemap migrated, but I don't know anything about
PyPi administrative operations.

Is there a fundamental problem because of its size?

—
Reply to this email directly or view it on GitHub
#5136 (comment)
.

[tacaswell]

If I recall, a while ago they bumped the size on behalf of us (which is why 1.3.1 onward has not been flagged).

[WeatherGod]

Right, but I don't know how much space they allocated. The Basemap package
is much larger than matplotlib's package. I'll start looking into it
tonight. I might need to split basemap into two packages because the data
portion almost never gets updated. We shall see.

On Thu, Sep 24, 2015 at 5:12 PM, Thomas A Caswell notifications@github.com
wrote:

If I recall, a while ago they bumped the size on behalf of us (which is
why 1.3.1 onward has not been flagged).

—
Reply to this email directly or view it on GitHub
#5136 (comment)
.

[tacaswell]

attn @mdboom

[mdboom]

I've uploaded the three tarballs in question to PyPI. That should address any issues with PIP. We've been uploading newer tarballs and wheels (since 1.4.0) to PyPI anyway.

Also created #5227 to put the final nail in the SourceForge coffin.