pypkgfreeze
Python's npm install --save
Automatically inserts your currently used package versions to setup.py.
Example
Old setup.py
from setuptools import setup
test_req = ['pytest', ]
setup(
name='pypkgfreeze',
install_requires=[
"Click",
],
tests_require=test_req,
extras_require={
'test': test_req
}
)
New setup.py
from setuptools import setup
test_req = ['pytest==4.0.2', ] # ADDED VERSION HERE
setup(
name='pypkgfreeze',
install_requires=[
"Click==7.0", # AND HERE
],
tests_require=test_req,
extras_require={
'test': test_req
}
)
Usage
pkgfreeze. It's that simple.
Installation
pip install pypkgfreeze
Contributing
Thanks! Please read the CONTRIBUTING.md file.
Metadata
Release files for pypkgfreeze 0.1.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pypkgfreeze-0.1.6.tar.gz | 2.5 kB | Without provenance | Details for pypkgfreeze-0.1.6.tar.gz |
Release files / pypkgfreeze-0.1.6.tar.gz
| Download URL | pypkgfreeze-0.1.6.tar.gz |
|---|---|
| Size | 2.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
57f08f847cf6b013cd7ae24196aee84a1a05633463a2af25adb3dbef6ecfa56f
|
|
BLAKE2b-256 checksum How to use checksums |
a1f83eb3eed4136bbbec0d78d2232d50e830acaf181fd1eec868f3eab5bc94f4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.4.0 requests-toolbelt/0.9.1 tqdm/4.36.1 CPython/3.6.7
|
Security for pypkgfreeze 0.1.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.