-
Notifications
You must be signed in to change notification settings - Fork 155
Make pip installable #256
Comments
I now see that this is actually uploaded to pypi as https://pypi.python.org/pypi/ArcREST_Package since the name in setup.py is different than on pypi, this is a little problematic but a good first step. |
And it doesnt actually install from pypi either 😱
|
@pykler We will take a look. |
@pykler You can now do: |
Yes doing that doesn't work. So the package uploaded to pypi is broken and
|
@pykler it works for me. |
@pykler please post your error. Make sure you aren't using a cached version. I removed the old versions this morning. |
works now, thanks. Can you please add the pip install command to the readme, it will make it easier for people to find since the pypi name is different from the package name. |
Also the latest version is now 3.5.6 as of pypi, so another thing to perhaps add to the README. |
Ideally, it should be installable with either command:
or
Also, |
It bothered me that installation by git repository URL downloads the code and attempts to install, but fails because of the incorrect structure of this project. I thought that pip must have (or should have) some way to specify that it should look in a different directory. It does. It just needs a specially formatted addition to the URL. The command using the URL with a specially formatted fragment suffix for installing the version 3.5.3 tag (Hey! Where's the 3.5.6 tag‽) is:
Version 3.5.6 may be installed (even though it's not been tagged), by installing from the default branch:
Although this information will help others install ArcREST with its current directory structure, I hope that doesn't keep the development team from correcting the layout. |
Currently this repo is not directly installable, it is neither uploaded to pypi nor is in installable with the following expression
Similarly the source archives are not. This is because setup.py is not at the root of the repo.
Another issue, this repo is named ArcRest which is a name that is already taken in pypi, so sticking with this name moving forward will only make things more problematic.
Steps to solve these issues
The text was updated successfully, but these errors were encountered: