-
-
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
poetry v1.3.0 #77
poetry v1.3.0 #77
Conversation
…nda-forge-pinning 2022.12.09.20.17.28
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 ( |
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 |
…nda-forge-pinning 2022.12.10.21.07.48
conda-forge/poetry-plugin-export-feedstock#8 and conda-forge/poetry-plugin-export-feedstock#9 went to Need to wait for a
|
regarding |
Regarding |
recipe/meta.yaml
Outdated
- tomlkit >=0.11.1,<1.0.0,!=0.11.2,!=0.11.3 | ||
- trove-classifiers >=2022.5.19 | ||
- virtualenv >=20.4.3,<21.0.0,!=20.4.5,!=20.4.6 # [not win or py!=39] | ||
- xattr >=0.10.0,<0.11.0 # [darwin] |
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.
This is the one I see no way around -- we can't be noarch.
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.
Does installing xattr break non-osx?
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.
Yes, xattr doesn't exist for win:
https://github.com/conda-forge/xattr-feedstock/blob/main/recipe/meta.yaml#L16
And I would hesitate to override the upstream choices in general to too great a degree.
- html5lib >=1.0,<2.0 | ||
- shellingham >=1.1,<2.0 | ||
- tomlkit >=0.7.0,<1.0.0 | ||
- importlib-metadata >=4.4,<5.0 # [py<310] |
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.
This could be noarch if everything else could be.
Co-authored-by: Ben Mares <services-git-throwaway1@tensorial.com>
Regarding poetry-core: |
Co-authored-by: Ben Mares <services-git-throwaway1@tensorial.com>
# `poetry` entry point fails without this: | ||
- lockfile >=0.9 |
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.
I understand that this is necessary, but I'm confused how Poetry works when this isn't an explicit dependency. Do you understand where it's coming from? Maybe there is a missing dependency from filelock
or something?
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.
I reported this upstream in python-poetry/poetry#7171. Let's see what they say.
I also think it's a problem regardless of whether this should come from another dependency because it's an explicit dependency.
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.
Good point, explicit dependencies should definitely be included by the package using them. But it's probably also an implicit dependency which is missing somewhere on CF... I can try to have a look...
Any ideas? |
I suspect we're missing something from cross-compilation on arm64. We should be able to compare with some other generic recipe with osx-arm64 enabled. I have to go right now, be back in an hour or so. |
Perfect, thanks @maresb! |
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.
Seems ready. I'll automerge.
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.
Seems ready. I'll automerge.
Huh? What's going on? Our commits here have landed in EDIT: Sorry, I seem to have been confused. I think I was looking at the file history, there is a merge commit. |
While the automerge action was running, there was a 500 failure in the GH API call to the merge endpoint. I can open a PR in the automerge repo to try and give a better stack trace. Perhaps for here we should run @conda-forge-admin, please rerun bot to clear things up and see where that leaves us. Then if there's no build, open a new PR with an empty commit? |
Ah, crap! I meant to remove the @ |
BTW I tracked down the implicit |
automerged PR by conda-forge/automerge-action
I just reset the head on |
That's not what I had in mind and not safe here. The automerge bot is only for recipes where the dependencies very rarely change. I just wanted to automerge this particular PR, but no need now |
Thanks for merging! I think I wasn't clear about what I meant in my previous message. I wasn't proposing enabling automerge here. Rather, I noticed a bug in the stack trace of the automerge-action which I'd like to fix with a PR. |
Sorry, I misunderstood. I see that now what you meant. The risks of girhubbing with my phone... |
If the only reason this isn't noarch anymore is dependencies, you could do something like outlined here: conda-forge/conda-forge.github.io#1839 |
We can give that a try. It would certainly be nice to go back to to noarch. |
Great, I’ll make a PR tomorrow |
Do we know if it's safe to install |
Looking into it... |
I looks like it. |
It is very likely that the current package version for this feedstock is out of date.
Checklist before merging this PR:
license_file
is packagedInformation about this PR:
@conda-forge-admin,
please add bot automerge
in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.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.Closes: #72
Closes: #73
Closes: #74
Pending Dependency Version Updates
Here is a list of all the pending dependency version updates 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 by source code inspection shows a discrepancy between it and the the package's stated requirements in the meta.yaml.
Packages found by source code inspection but not in the meta.yaml:
Packages found in the meta.yaml but not found by source code inspection:
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. 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/3661965370, please use this URL for debugging.