This python package provide a simple wrapper around Distribute to handle private projects. It is mostly intended for use in a package’s setup.py script.
It provides the following features:
Using a private package index when fetching package dependencies during python setup.py install
Restricting the register and upload commands to a private package index, or to disable them completely
Easy support for authenticated URLs when accessing the index.
Compatibility
The restricted_pkg package requires Distribute, and supports Python 2.6 and later (including Python3).
Usage
In your setup.py script, ensure you have the following lines:
from setuptools import find_packages
from restricted_pkg import setup
setup(
...,
private_repository="https://@myrepo.example.tld/path/to/repo",
install_requires=[
"distribute",
"restricted_pkg",
],
)
Metadata
Release files for restricted_pkg 1.1.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 | |
|---|---|---|---|---|
| restricted_pkg-1.1.2.tar.gz | 10.4 kB | Without provenance | Details |
Release files / restricted_pkg-1.1.2.tar.gz
| Download URL | restricted_pkg-1.1.2.tar.gz |
|---|---|
| Size | 10.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aeb0ed2b8e1ac8fdbf73549357fdc11d3dde62963122bfdb9affda648920981d
|
|
BLAKE2b-256 checksum How to use checksums |
ac635ac2d21284e642d9963e63c9bbe415d61f5f545df8c3e92d4dc82fe84495
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for restricted_pkg 1.1.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.