[DEV] Bump to 1.2.0b2

[maresb]

Upstream diff

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

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

[maresb]

@conda-forge-admin, please rerender

[xylar]

Looks right to me! Thanks @maresb!

[xylar]

Hmm, it looks like poetry-plugin-export depends on poetry
https://github.com/conda-forge/poetry-plugin-export-feedstock/blob/main/recipe/meta.yaml#L21
and this version of poetry depends on poetry-plugin-export

poetry-feedstock/recipe/meta.yaml

Line 29 in 0dc31c1

- poetry-plugin-export >=1.0.4,<2.0.0

Such circular dependencies are allowed on pypi but not in conda packages.

The other problem is that I don't know how well it will work for a non-dev package (poetry-plugin-export) to require a dev package (this poetry).

[maresb]

Yes, this is the same circular dependency I was complaining about in #65.

What do you mean by a "non-dev" package? At least the label for poetry-plugin-export is poetry_dev.

Maybe I should complain upstream about the circular dependency.

[maresb]

It looks like the build is failing due to some missing packages.

[xylar]

I noticed after the fact that poetry-plugin-export was on poetry_dev so that's fine. That's probably necessary for any package that has a dependency on a *_dev label.

[xylar]

Yes, the missing dependencies need to be built (or the recipes added) but the one that has me worried is:

package poetry-plugin-export-1.0.4-pyhc6ef2e2_0 requires poetry >=1.2.0b1dev0,<2.0.0, but none of the providers can be installed

I don't see any way to fix this unless poetry-plugin-export can be made to depend on poetry-core instead of poetry. So, yes, I think you (we) probably need to complain upstream.

[maresb]

Hmm, good point. These circular dependencies are very confusing. Conda tries to set up an environment for building Poetry, installs poetry-plugin-export as a dependency, and then ends up installing Poetry itself as a subdependency. I don't know much about the implementation details of Conda, but this does indeed seem very bad.

[maresb]

WIP for missing platformdirs:
conda-forge/platformdirs-feedstock#11

[maresb]

platformdirs is complete

[maresb]

The remaining dependencies seem to now be in order. The circular dependency is still problematic. Hopefully something will happen with python-poetry/poetry#5980

[xylar]

closed via #71