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 am interested in PEP 751 so that developers can leverage the official python pip package manager to install and manage dependencies with strong security assurances.
I'm creating this issue to track the implementation of this matter as I am highly interested in this.
As pip is a volunteer-based project, contributions are welcome. This is definitely something we want to do, so it's just a matter of someone finding the time to implement it.
ichard26
changed the title
Implementation of PEP 751
Implement PEP 751 aka standardized lockfiles
Apr 15, 2025
Our current install process is with pip in `install.sh`. `install.sh`
makes for an easy installation process, but using pip can mean that
users can get different installations of dbt-mcp. The best way to fix
this would be to install the app from the `uv.lock` file, not with pip.
However, this would require that users have uv installed. In the future,
we can use [uv
export](https://github.com/astral-sh/uv/issues/12584?utm_source=chatgpt.com)
and install from pylock.toml with pip, but [that isn't supported
yet](pypa/pip#13334). In the meantime, pinning
all dependencies should help provide for a more consistent install.
What's the problem this feature will solve?
I am interested in PEP 751 so that developers can leverage the official python pip package manager to install and manage dependencies with strong security assurances.
I'm creating this issue to track the implementation of this matter as I am highly interested in this.
Describe the solution you'd like
pip implementing PEP 751.
Alternative Solutions
.
Additional context
https://peps.python.org/pep-0751/
Code of Conduct
The text was updated successfully, but these errors were encountered: