-
Notifications
You must be signed in to change notification settings - Fork 394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider moving the pip package away from sourceforge #198
Comments
I've found this too, it makes installation of basemap a bit of a pest when using pip. And I'd echo the sentiments about sourceforge as well. |
These are valid points, and it is something to consider. Previously, the On Tue, Aug 11, 2015 at 5:17 AM, Mark Muetzelfeldt <[email protected]
|
Relevant thread : matplotlib/matplotlib#2715 Maybe file size limit of 50MB? |
Thread rezz-ing. |
If you can wait until Warehouse is ready (scheduled to be early 2016), we'll have the ability to allow larger file sizes for specific projects so we can whitelist particular ones to have larger upload limits (our theoretical maximum will be several GB... but at some point we start running into problems with the cost of storing multiple releases of giant packages). In any case, 130MB for a well established project like matplotlib shouldn't be an issue once we can loosen the restrictions on a per project basis. |
@dstufft Is Warehouse ready to be used for basemap now? As far as I can see it's still in development but at least partially operational. |
Yea, you can upload to Warehouse now, but you'll want to be aware of pypi/warehouse#1194. |
Is that true even if the package was never hosted on pypi directly? basemap On Wed, May 18, 2016 at 12:45 PM, Donald Stufft [email protected]
|
Yea, but you only have to do it once each time you upload (and once the issue is fixed, never again). |
Basemap can at the moment apparently not be installed easily via pip. (see matplotlib/basemap#251 and matplotlib/basemap#198) Signed-off-by: Ramon Fuentes Franco <[email protected]>
What is the current stage of this issue? I an trying to write some tutorials using basemap, and I want to minimilise the effort of installing it. |
any news, @WeatherGod ? I'm also in a similar situation of @quang-ha:
|
# v1.2.0rel
$ pip install https://github.com/matplotlib/basemap/archive/v1.2.0rel.tar.gz
# v1.1.0
$ pip install https://github.com/matplotlib/basemap/archive/v1.1.0.tar.gz |
PR #433 discusses about this issue. |
I solved this by uninstalling the conda and reinstalling, defining on installation the conda path on variable environment. After, at settings on your project, set the project interpreter to C:\Users\the_user_name\anaconda3\python.exe, then try to install the basemap. It was the only way I got this, after many tries and bugs with pip I tried with conda and that's it. |
I'm not sure I understand. I have just installed anaconda after a few days of pip problems. not sure where to go from here |
Currently, the url for basemap in pypi points at https://downloads.sourceforge.net/project/matplotlib/matplotlib-toolkits/basemap-1.0.7/basemap-1.0.7.tar.gz. This means that in order to install basemap, one has to type the rather scary-looking and lengthy
pip3 install --allow-external basemap --allow-unverified basemap basemap
. Given this and some relatively shady stuff sourceforge have engaged in recently, I think it's a good idea for you to move the distribution and update the pypi listing accordingly.The text was updated successfully, but these errors were encountered: