OVERVIEW
- a experiment for verifying if two pypi packages can have the same {namespace} or not
STRUCTURE
- PACKAGES
- one : demo_same_package/one.py
- two : demo_same_package/two.py
THIS PACKAGE
- two
EXPECTATION
- PACKAGE INSTALLATION
pip install demo-same-package-one
pip install demo-same-package-two
- EXPECTED RESULTS
- the source code would be
- demo_same_package/
- one
- two
- demo_same_package/
- the source code would be
1 maintainer
Metadata
1 maintainer
Release files for demo-same-package-two 0.0.2
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 | |
|---|---|---|---|---|
| demo-same-package-two-0.0.2.tar.gz | 2.5 kB | Without provenance | Details |
Release files / demo-same-package-two-0.0.2.tar.gz
| Download URL | demo-same-package-two-0.0.2.tar.gz |
|---|---|
| Size | 2.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f8a7375deea1fce4ab2f6eb6c6c8b33e318f866c3baefbab940c197553a7175c
|
|
BLAKE2b-256 checksum How to use checksums |
2c00315991b2b90339a1cf73a97138ce42ee4ca15f461e042cc7b068b9c4445c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.7
|
Security for demo-same-package-two 0.0.2
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.
