setupextras

Additional common setuptools helpers - for Python.
Introduction
TODO
Install
Install using pip:
$ pip install setupextras
Use
Very basic example:
# =========================================
# IMPORTS
# --------------------------------------
import os
import json
import setuptools
import setupextras
# =========================================
# PACKAGE
# --------------------------------------
name = 'foo'
version = '1.0.0'
description = 'A foo library.'
keywords = [
'foo',
'bar',
]
packages = setupextras.get_packages()
data_files = setupextras.get_data_files(['*.*'], os.path.join(name, 'tests', '__fixtures__'))
requirements = setupextras.get_requirements()
readme = setupextras.get_readme()
config = {
'name': name,
'version': version,
'description': (description),
'keywords': keywords,
'author': 'Jonas Grimfelt',
'author_email': 'grimen@gmail.com',
'url': 'https://github.com/grimen/python-{name}'.format(name = name),
'download_url': 'https://github.com/grimen/python-{name}'.format(name = name),
'project_urls': {
'repository': 'https://github.com/grimen/python-{name}'.format(name = name),
'bugs': 'https://github.com/grimen/python-{name}/issues'.format(name = name),
},
'license': 'MIT',
'long_description': readme,
'packages': packages,
'data_files': data_files,
'install_requires': requirements,
}
print('CONFIG {0}'.format(json.dumps(config, indent = 4)))
# =========================================
# MAIN
# --------------------------------------
setuptools.setup(**config)
Test
Clone down source code:
$ make install
Run colorful tests, with only native environment (dependency sandboxing up to you):
$ make test
Run less colorful tests, with multi-environment (using tox):
$ make test-tox
About
This project was mainly initiated - in lack of solid existing alternatives - to be used at our work at Markable.ai to have common code conventions between various programming environments where Python (research, CV, AI) is heavily used.
License
Released under the MIT license.
Metadata
Release files for setupextras 0.1.5
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 |
|---|---|---|---|---|
| setupextras-0.1.5.tar.gz | 13.1 kB | Without provenance | Details for setupextras-0.1.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| setupextras-0.1.5-py3-none-any.whl | Python 3 | none | any | Details for setupextras-0.1.5-py3-none-any.whl |
Total release size: 29.1 kB
Release files / setupextras-0.1.5.tar.gz
| Download URL | setupextras-0.1.5.tar.gz |
|---|---|
| Size | 13.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2c21d99d01fdf3340a67066fcd0a97aae3f2f24b305d6c11b196526faa91df1a
|
|
BLAKE2b-256 checksum How to use checksums |
2bfce84b4f4ef49f669585ea8682899eead0406a688bf4d12d86c4da93d6aa8d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.5
|
Release files / setupextras-0.1.5-py3-none-any.whl
| Download URL | setupextras-0.1.5-py3-none-any.whl |
|---|---|
| Size | 16.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b065860551e9dd422efe35c15dd8cd7edf9ebaeb1309a7bca5475b6010f926aa
|
|
BLAKE2b-256 checksum How to use checksums |
182c8ffaab19cde5c47a04554d675c0de31ad9ae8da6261dac8808e2a178f50d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.5
|
Security for setupextras 0.1.5
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.