You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the reasons we didn't switch to poetry entirely is the fact we still support python 2.7 and 3.5. And we are planning to do so until EOL of ESP-IDF 4.3 this December.
IIRC, we decided to exclude poetry.lock, because the lock file does not always work on all platforms and different Python versions, because not all packages provide all the metadata on PyPI.
What is your main difficulty with packaging the component manager for nix? Could you use setup.py there?
@corpix In a coming release of 2.0.0 we will remove setup.py, but still won't add a lock file. What is the main problem of packaging without a lock file?
Related area
git
Is your feature request related to a problem?
There is no lock file in source control. This makes packaging this tool difficult (I do update this environment https://github.com/mirrexagon/nixpkgs-esp-dev)
Describe the solution you'd like
I see
.gitignore
sayspoetry.lock
was removed because of tests. Maybe this could be done during test environment preparation?Describe alternatives you've considered
No response
Additional context
No response
I have checked existing list of Feature requests and I have provided enough information.
The text was updated successfully, but these errors were encountered: