-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
mdanalysis v1.0.1 #28
mdanalysis v1.0.1 #28
Conversation
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( I do have some suggestions for making it better though... For recipe:
Documentation on acceptable licenses can be found here. |
Picked from https://spdx.org/licenses/ as recommended by linter.
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@richardjgowers @IAlibay do we need to restrict the biopython version in the meta.yml?
Blocking until we know.
From setup.py
I think we need some serious updating of our dependencies in meta.yml, in particular for 1.0.1 anything related to Py 2 support. |
|
No sure why pip was not able to find numpy for pypy:
|
Yeah looks like we'll need to at very least pin numpy (seems like it's picking up 1.20?) and biopython? Future proofing wise, we probably also want to pin on cython < 1.0? |
Same problem with 3.6 cpython
|
I think so (for the build). For the conda package itself, cython isn't a dep, is it? |
You're right, it isn't (maybe in 2.0 though 🙃 ). |
- add constraints from the 1.0.1 setup.py - added funcsigs and mock - gsd was doubled up: removed the version that did not have the `[not win]` comment... not sure about this
I added package constraints directly to this PR (didn't manage to do a PR against the PR). Please have a look. @richardjgowers why did we have |
These package constraints are a bit iffy. Anything that was "for Python 2" should really not apply for conda packages built against Python 3. We will almost certainly annoy users when we ship conda packages that tell them that they have to downgrade joblib to < 0.15.0. Can we write the restriction in a way that differentiates between Py 2 and Py 3 builds? numpy is supposedly handled differently although I don't understand how pin_compatible() really works. |
Agreed, although because these restrictions were imposed in setup.py, we haven't tested a version of 1.0.1 that goes outside these limits. For sure numpy 1.19+ is going to fail (I don't think Tyler's fixes were backported?). Joblib and biopython are unlikely to have broken anything, but we'd have to test anyway. |
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipe:
|
We're going to have to explicitly define the python versions here since it seems to have added 3.9 (which we don't support in 1.0.x), it's not immediately clear to me that we can add support back for 3.5 or 2.7 though. |
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
Ok so it looks like pypy doesn't work, but I'm not sure we have checked that ourselves, so we can drop that. Windows is failing complaining about something in MANIFEST being an absolute path which is confusing. Then 3.9 builds are also failing. what fun! |
@richardjgowers is there any way we can restrict the maximum python version to 3.8? 3.9 isn't in our CI matrix and if I remember correctly a bunch of optional deps don't work on it yet. |
@richardjgowers and @orbeckst we should probably act on this soon-ish. Do we want to go ahead with it knowing that it won't work on Windows/pypy/some newer versions of some packages, or do we want to kill 1.0.1 and quickly replace it with 1.0.2? I'd be tempted to vote for the former so that it gives us a little bit of time to roll out a stable 1.0.2 that works w/ nsgrid fixed. If we do go with the 1.0.1 then maybe I should go ahead and release the tests on pypi now? |
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipe:
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
@conda-forge-admin, please rerender |
…da-forge-pinning 2021.02.26.15.36.03
It is very likely that the current package version for this feedstock is out of date.
Notes for merging this PR:
Checklist before merging this PR:
license_file
is packagedNote that the bot will stop issuing PRs if more than 3 Version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.
NEW: If you want these PRs to be merged automatically, make an issue with
@conda-forge-admin,
please add bot automerge
in the title and merge the resulting PR. This command will add our new bot automerge feature to your feedstock!If this PR was opened in error or needs to be updated please add the
bot-rerun
label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase@conda-forge-admin, please rerun bot
in a PR comment to have theconda-forge-admin
add it for you.This PR was created by the regro-cf-autotick-bot.
The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. If you would like a local version of this bot, you might consider using rever. Rever is a tool for automating software releases and forms the backbone of the bot's conda-forge PRing capability. Rever is both conda (
conda install -c conda-forge rever
) and pip (pip install re-ver
) installable.Finally, feel free to drop us a line if there are any issues!
This PR was generated by https://github.com/regro/autotick-bot/actions/runs/582482804, please use this URL for debugging
Here is a list of all the pending dependencies (and their versions) for this repo. Please double check all dependencies before merging.
Dependency Analysis
Please note that this analysis is highly experimental. The aim here is to make maintenance easier by inspecting the package's dependencies. Importantly this analysis does not support optional dependencies, please double check those before making changes. If you do not want hinting of this kind ever please add
bot: inspection: false
to yourconda-forge.yml
. If you encounter issues with this feature please ping the bot teamconda-forge/bot
.Analysis of the source code shows no discrepancy between the library's imports and the package's stated requirements in the meta.yaml.