Skip to content
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

Merged
merged 10 commits into from
Dec 11, 2022
Merged

poetry v1.3.0 #77

merged 10 commits into from
Dec 11, 2022

Conversation

regro-cf-autotick-bot
Copy link
Contributor

@regro-cf-autotick-bot regro-cf-autotick-bot commented Dec 10, 2022

It is very likely that the current package version for this feedstock is out of date.

Checklist before merging this PR:

  • Dependencies have been updated if changed: see upstream
  • Tests have passed
  • Updated license if changed and license_file is packaged

Information about this PR:

  1. Feel free to push to the bot's branch to update this PR if needed.
  2. The bot will almost always only open one PR per version.
  3. 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.
  4. 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 bot automerge feature to your feedstock.
  5. 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 the conda-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.

Name Upstream Version Current Version
poetry-core 1.4.0 Anaconda-Server Badge

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 your conda-forge.yml. If you encounter issues with this feature please ping the bot team conda-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:

  • dulwich
  • urllib3
  • autovizwidget
  • platformdirs
  • filelock

Packages found in the meta.yaml but not found by source code inspection:

  • clikit
  • cachy
  • ptyprocess

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.

@conda-forge-linter
Copy link

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 (recipe) and found it was in an excellent condition.

@conda-forge-linter
Copy link

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 (recipe) and found some lint.

Here's what I've got...

For recipe:

  • requirements: run: cachecontrol = >=0.12.9,<0.13 should not contain a space between relational operator and the version, i.e. cachecontrol =>=0.12.9,<0.13

@conda-forge-linter
Copy link

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 (recipe) and found it was in an excellent condition.

@xylar
Copy link
Contributor

xylar commented Dec 10, 2022

@conda-forge-admin, please rerender

@xylar
Copy link
Contributor

xylar commented Dec 10, 2022

@ocefpaf and @maresb, please have a careful look. There are a lot of dependency changes here and I think we can't get away with noarch anymore.

@xylar
Copy link
Contributor

xylar commented Dec 10, 2022

conda-forge/poetry-plugin-export-feedstock#8 and conda-forge/poetry-plugin-export-feedstock#9 went to poetry_dev instead of main and need to be rebuilt for main.

Need to wait for a poetry-core 1.4.0 build

trove-classifiers (https://pypi.org/project/trove-classifiers/) has not been built on conda-forge and needs a staged recipe.

@xylar
Copy link
Contributor

xylar commented Dec 10, 2022

@xylar
Copy link
Contributor

xylar commented Dec 10, 2022

Regarding trove-classifiers:
conda-forge/staged-recipes#21504

recipe/meta.yaml Show resolved Hide resolved
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]
Copy link
Contributor

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.

Copy link
Contributor

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?

Copy link
Contributor

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]
Copy link
Contributor

@xylar xylar Dec 10, 2022

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>
@xylar
Copy link
Contributor

xylar commented Dec 11, 2022

Regarding poetry-core:
conda-forge/poetry-core-feedstock#35

recipe/meta.yaml Outdated Show resolved Hide resolved
xylar and others added 2 commits December 11, 2022 10:56
Co-authored-by: Ben Mares <services-git-throwaway1@tensorial.com>
Comment on lines +59 to +60
# `poetry` entry point fails without this:
- lockfile >=0.9
Copy link
Contributor

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?

Copy link
Contributor

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.

Copy link
Contributor

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...

@xylar
Copy link
Contributor

xylar commented Dec 11, 2022

export SRC_DIR=/Users/runner/miniforge3/conda-bld/poetry_1670754476345/work
/Users/runner/miniforge3/conda-bld/poetry_1670754476345/work/conda_build.sh: line 4: /Users/runner/miniforge3/conda-bld/poetry_1670754476345/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/bin/python: Bad CPU type in executable

Any ideas?

@maresb
Copy link
Contributor

maresb commented Dec 11, 2022

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.

@xylar
Copy link
Contributor

xylar commented Dec 11, 2022

Perfect, thanks @maresb!

Copy link
Contributor

@xylar xylar left a 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.

Copy link
Contributor

@xylar xylar left a 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.

@xylar xylar added the automerge Merge the PR when CI passes label Dec 11, 2022
@maresb
Copy link
Contributor

maresb commented Dec 11, 2022

Huh? What's going on? Our commits here have landed in main without a merge commit, and this PR is still open.

EDIT: Sorry, I seem to have been confused. I think I was looking at the file history, there is a merge commit.

@maresb
Copy link
Contributor

maresb commented Dec 11, 2022

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?

@conda-forge-linter conda-forge-linter added the bot-rerun Instruct the bot to retry the PR label Dec 11, 2022
@maresb
Copy link
Contributor

maresb commented Dec 11, 2022

Ah, crap! I meant to remove the @

@maresb maresb removed the bot-rerun Instruct the bot to retry the PR label Dec 11, 2022
@maresb
Copy link
Contributor

maresb commented Dec 11, 2022

BTW I tracked down the implicit lockfile dependency to conda-forge/cachecontrol-feedstock#15. That was really confusing, since I wasn't expecting a yanked package!

maresb pushed a commit to maresb/poetry-feedstock that referenced this pull request Dec 11, 2022
automerged PR by conda-forge/automerge-action
@maresb maresb closed this Dec 11, 2022
@maresb maresb reopened this Dec 11, 2022
@maresb maresb removed the automerge Merge the PR when CI passes label Dec 11, 2022
@maresb
Copy link
Contributor

maresb commented Dec 11, 2022

I just reset the head on main. Let's merge this by hand after checks pass, and then I'll open a PR in conda-forge/automerge-action.

@xylar
Copy link
Contributor

xylar commented Dec 11, 2022

then I'll open a PR in conda-forge/automerge-action.

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

@xylar xylar merged commit 84ff470 into conda-forge:main Dec 11, 2022
@maresb
Copy link
Contributor

maresb commented Dec 11, 2022

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.

@xylar
Copy link
Contributor

xylar commented Dec 11, 2022

Sorry, I misunderstood. I see that now what you meant. The risks of girhubbing with my phone...

@regro-cf-autotick-bot regro-cf-autotick-bot deleted the 1.3.0_h5f1e7e branch December 11, 2022 14:16
@BastianZim
Copy link
Member

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

@xylar
Copy link
Contributor

xylar commented Dec 15, 2022

We can give that a try. It would certainly be nice to go back to to noarch.

@BastianZim
Copy link
Member

Great, I’ll make a PR tomorrow

@BastianZim
Copy link
Member

Do we know if it's safe to install tomli everywhere, including 3.11?

@BastianZim BastianZim mentioned this pull request Dec 16, 2022
5 tasks
@xylar
Copy link
Contributor

xylar commented Dec 16, 2022

Do we know if it's safe to install tomli everywhere, including 3.11?

Looking into it...

@xylar
Copy link
Contributor

xylar commented Dec 16, 2022

I looks like it. tomli is noarch on conda-forge and doesn't exclude 3.11. Then, there are these lines in poetry:
https://github.com/python-poetry/poetry/blob/1.3.0/src/poetry/utils/_compat.py#L11-L15
So it just won't get used in py 3.11.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants