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
I would like to know whether PEP 751 is being considered by pipx developers and how pipx might use the proposed "pylock.toml" file.
The PEP rational begins "The format is designed so that a locker which produces the lock file and an installer which consumes the lock file can be separate tools." Because package locking is a need for Python applications and pipx is a (the?) primary PyPA project for installing Python applications, I guess pipx should be a consumer of lock files. Is that planned?
One thing I'm not clear on with the PEP is whether "pylock.toml" is meant to be part of an application package (i.e. in the distribution on pypi). Is that the idea? How else would pipx get to consume it?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I would like to know whether PEP 751 is being considered by pipx developers and how pipx might use the proposed "pylock.toml" file.
The PEP rational begins "The format is designed so that a locker which produces the lock file and an installer which consumes the lock file can be separate tools." Because package locking is a need for Python applications and pipx is a (the?) primary PyPA project for installing Python applications, I guess pipx should be a consumer of lock files. Is that planned?
One thing I'm not clear on with the PEP is whether "pylock.toml" is meant to be part of an application package (i.e. in the distribution on pypi). Is that the idea? How else would pipx get to consume it?
Beta Was this translation helpful? Give feedback.
All reactions