Open MrLixm opened 2 months ago
The code in question already has been removed from the main branch so I guess this will go away at next release.
Meanwhile I suppose no-one else cares about python 3.7 - which is a year past end of life. Perhaps you shouldn't either?
Hey thanks I guess that is good news. However by "code in question" do you mean the functools.lru_cache
call ? Even if removed I guess there is still something weird happening right ?
As for python-3.7 I am working in the VFX industry where we haven't even moved entirely from python-2.7, so just to say it does matter for some people ! If poetry doesn't support python-3.7 venv fine but then it should be mentioned in the doc so I can track down an old version that still supports it.
Even if removed I guess there is still something weird happening right ?
If you want to know whether the main branch of poetry fixes your issue you should try it.
I indeed confirm the main branch works: https://github.com/knotsanimation/test_package2/actions/runs/9670244656/job/26678592345 So thanks for that !
However my question was more that maybe the issue is still here and is just not triggered anymore but I guess that is up to you maintainers to decide.
I am fine with closing this issue and I will eagerly wait for the next release then. Thanks again, Liam.
I'm experiencing this too in our CI where we still provide support for Python 3.7 in our codebase. If Poetry is no longer supporting 3.7 venvs, does it mean that it also won't be able to build for Python 3.7?
this issue is fixed in the main branch and should be closed
Description
Hello, I have a project on which I am using poetry for my dependency management and that I would like to have my unittest running in CI. For the CI I am using GitHub action with their GitHub-hosted runners.
I am aiming to test the project with the 2 min/max python version: python-3.7 and python-3.11.
However it happens that I cannot install my dependencies using
poetry install --extras tests
when using python-3.7 for my venv. It seems a weird conflict occurs where I get a Exception due to trying to run python-3.10 code with a python-3.7 interpreter (or maybe the other way around ?):Of course everything works fine when running with python-3.11.
Until now this issue have been a nightmare to debug and I tried a lot of options to debug it. I though it was initially related to the
setup-python
action caching but removing it (or even creating a new repo without it in the first place) did not changed the outcome. I also tested poetry 1.7 and different 1.8 versions but no changes.During my investigation I stumbled upon https://github.com/actions/setup-python/issues/846 which is partly related but as mentioned it doesn't seems to be a caching problem. At that point I don't care if I use caching or not I just want my CI to work :/
So I'm first opening an issue here but let me know if the issue actually seems to be more on the GitHub action side and potentially
setup-python
rather than poetry.resources
Best, Liam.
Workarounds
No workaround found yet.
Poetry Installation Method
pipx
Operating System
Unbuntu 22.04.4 LTS
Poetry Version
1.8
Poetry Configuration
Python Sysconfig
Example pyproject.toml
Poetry Runtime Logs