Are the strong version limitations on almost all dependencies needed? This gives version clashses for packages that want to use poetry:

conda-forge/pkgconfig-feedstock#27

Comment:

I have been trying to pull the poetry package from conda-forge for a OSX. However, it will never resolve.

base ❯ conda install -c conda-forge poetry
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: / failed

CondaError: KeyboardInterrupt


~ 1h 2m 34s

It ran for over 1 hour. This is a fresh install of Anaconda with only conda upgrade conda anaconda --a being run. I have tried numerous times over the past two days. I have also added conda-forge for the channels and set priority to strict and still no luck.

Comment:

I would like to build the latest beta version v1.2.0b2. However it now depends on ^1.0.4 of a package called poetry-plugin-export. In a partially circular dependency, that relies on poetry ^1.2.0b1.

To complicate matters further, poetry-plugin-export doesn't have a license file.

I think I should make a new feedstock for poetry-plugin-export, but that must target the dev channel sources. I'm not sure if that's allowed in staged-recipes.

As you can see, the situation is unfortunately rather complicated. Any suggestions?

Comment:

Actually this is documentation, not a real issue. But since the procedure is not obvious during this awkward period where the most useful Poetry versions are in pre-release, I figure that this is a quick and easy way to put instructions where people will find them. (Feel free to close this if you have a better idea.)

As described in #57 (comment), if you want to create a Conda environment called pdev which contains Poetry v1.2.0b1 together with the latest poetry-core, run

mamba create --yes --name pdev -c conda-forge/label/poetry_dev -c conda-forge/label/cleo_dev -c conda-forge "poetry=1.2.0b1"

where conda also works in place of mamba.

Hi all,

First, thank you for creating this feedstock! It's been very helpful.

Having the ability to install v1.2 would be helpful for my own projects. I'd like to inquire as to the possibility of building it, perhaps with a separate label or branch as described in #56 (comment). Is this possible and what would it involve?

I've never contributed to a cf feedstock before, but if needed, I might be able to offer some help.

• I read the conda-forge documentation and could not find the solution for my problem there.

Issue:

$ conda list

$ conda info

Only by looking through the repo's code/scripts was I able to figure out wtf this dope repo does--need a better readme or at the very least a summary/intro to the readme.

Solution to issue cannot be found in the documentation.

• I checked the documentation.

Issue

python-poetry/poetry@c5ac467

Poetry has updated the importlib-metadata to >=1.6.0

importlib-metadata = { version = ">=1.6.0", python = "<3.8" }

Installed packages

NA

Environment info

NA

Comment:

Poetry has released 1.2.0rc2 and is going to finalize 1.2.0 soon. Can I request a cut of the latest release candidate so that I can test how downstream conda dependencies work under 1.2?

Solution to issue cannot be found in the documentation.

• I checked the documentation.

Issue

I cannot install version 1.3.2 of this package alongside Python 3.11, at least not on Linux.

mamba create --name temp python=3.11 poetry=1.3.2

The mamba error suggests that __osx is erroneously being listed as a dependency.

Looking for: ['python=3.11', 'poetry=1.3.2']

conda-forge/linux-64                                        Using cache
conda-forge/noarch                                          Using cache
Encountered problems while solving:
  - nothing provides __osx needed by poetry-1.3.2-osx_pyhd8ed1ab_0

Strangely, it installs just fine if I specify Python 3.10. These lines in the recipe listing __osx as a mandatory runtime dependency are a little funky, but the comment suggests they were added intentionally.

Installed packages

N/A

Environment info

active environment : temp
    active env location : /home/david/anaconda/envs/temp
            shell level : 2
       user config file : /home/david/.condarc
 populated config files : /home/david/anaconda/.condarc
          conda version : 22.11.1
    conda-build version : not installed
         python version : 3.10.8.final.0
       virtual packages : __archspec=1=x86_64
                          __cuda=11.4=0
                          __glibc=2.31=0
                          __linux=5.15.0=0
                          __unix=0=0
       base environment : /home/david/anaconda  (writable)
      conda av data dir : /home/david/anaconda/etc/conda
  conda av metadata url : None
           channel URLs : https://conda.anaconda.org/conda-forge/linux-64
                          https://conda.anaconda.org/conda-forge/noarch
          package cache : /home/david/anaconda/pkgs
                          /home/david/.conda/pkgs
       envs directories : /home/david/anaconda/envs
                          /home/david/.conda/envs
               platform : linux-64
             user-agent : conda/22.11.1 requests/2.28.1 CPython/3.10.8 Linux/5.15.0-58-generic ubuntu/20.04.5 glibc/2.31
                UID:GID : 1000:1000
             netrc file : None
           offline mode : False

Solution to issue cannot be found in the documentation.

• I checked the documentation.

Issue

Seeing this across a few conda-forge packages:

https://github.com/conda-forge/gotrue-feedstock/runs/17443079855

    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1381, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1354, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1304, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
  File "<frozen importlib._bootstrap>", line 1381, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1354, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1325, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 929, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 994, in exec_module
  File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
  File "/home/conda/feedstock_root/build_artifacts/gotrue_1696535357058/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/python3.12/site-packages/poetry/core/masonry/__init__.py", line 10, in <module>
    from .builder import Builder
  File "/home/conda/feedstock_root/build_artifacts/gotrue_1696535357058/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/python3.12/site-packages/poetry/core/masonry/builder.py", line 5, in <module>
    from poetry.core.utils._compat import Path
  File "/home/conda/feedstock_root/build_artifacts/gotrue_1696535357058/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/python3.12/site-packages/poetry/core/utils/_compat.py", line 8, in <module>
    import six.moves.urllib.parse as urllib_parse
ModuleNotFoundError: No module named 'six.moves'

Installed packages

n/a

Environment info

n/a

Additional comment:

No response

Additional comment:

No response