-
Notifications
You must be signed in to change notification settings - Fork 194
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
Installation instructions #49
Comments
Thank you for doing this review @martinfleis! Ad Naive installation Yes, pip install will also fail on Windows. My understanding is that it is not possible to pip install all GeoPandas dependencies and therefore MovingPandas suffers the same fate. I'll add Mac to the paragraph that warns Windows users. I'll look into the channel issue. Can you please point me towards the GeoPandas recommendations that you've mentioned? Ad Dev installation I'll change the Readme accordingly. Ad Version in conda-forge I'll try to get the 0.2 (noarch) release into conda-forge this weekend. |
Based on pyOpenSci review feedback #49
|
That is true, it takes a lot of manual effort to do it.
See the note in here: https://geopandas.readthedocs.io/en/latest/install.html#using-the-conda-forge-channel I've just realised that it is not clear that movingpandas is available on conda-forge. It might be worth it adding |
Fixed in c84e9c0 |
Based on your comment, I've removed defaults from the environment. However, I've run into issues on Windows: basically, importing geopandas fails because gdal imports fail. conda-forge/gdal-feedstock#269 (comment) states that
So, I guess I'll have to add a win-environment.yml and/or add specific instructions to the README. Is there any commonly used approach for handling this kind of issues? |
I was not even aware of this Windows issue as macOS/Ubuntu user. We should probably refer to is in geopandas docs as well. I'd say putting the content of that comment would be a good way of dealing with it. |
I've added all the install details I'm aware of 9440ba1 |
Hi @martinfleis. Trying to clean loose ends in this review. It looks like @anitagraser has indicated that this issue has been addressed (and you indicated a thumbs up :). Can this issue be closed? |
@jlpalomino I guess so, I am fine with the current solution. I'll close it and @anitagraser can reopen if needed. |
Again thanks for confirming @martinfleis! |
Hi,
this is a part of pyOpenSci/software-submission#18.
Naive installation
As a naive user, if I make a new python environment and do
pip install movingpandas
, the installation fails on Mac.Using
conda install -c anitagraser movingpandas
works, but you'll get a mixture of channels (conda-forge and defaults), which is known to cause issues. Moreover, you get geopandas from defaults in older version that is on conda-forge.It is worth documenting possible issues and workarounds (strict channel priority) as the default installation instructions do not follow GeoPandas recommendations.
Dev installation
Current dev installation instructions expect using Anaconda. I'd say that most dev people will just make a new environment using
conda env create -f environment.yml
, but it has to be derived from the Aanconda instructions. I'd just add a sentence saying that dev env should use environment.yml and keep Anaconda instructions as one of the options only.Minor question - conda installs movingpandas 0.1.dev2, while the review issue says
Version submitted: 0.2
. Should I assume that 0.2 will be released after the review?The text was updated successfully, but these errors were encountered: