ProjectSetup
Initialize your Python Project
Features
ProjectSetup helps you to get started with your Python Project as fast as possible.
It will handle these tasks for you:
initialize a python module named after your project
add Community Files
Readme.md
Contributing.md
CODE_OF_CONDUCT.md
issue_template.md
PULL_REQUEST_TEMPALTE.md
add important project files like LICENSE, setup.py, requirements.txt and more
initialize Sphinx documentation
prepare test-directory with a skipping dummy test
build a initial source distribution and python wheel
Some additional customizations are done for Jetbrains PyCharm IDE
To get a full list of all supported features, please read the `project wiki <https://github.com/michagrandel/ProjectSetup/wiki>`__.
Getting Started
Installing
pip install ProjectSetup
If this doesn’t work, try to download the code, extract the zip-file and run:
python setup.py install -r requirements.txt
How to run
To run the script, just use the quickstart.py-Script in the script-folder.
Customize the settings
To customize everything, you just need to edit the quickstart.py.
In future releases, you will be able to use a command line interface without needing to edit the script code.
Running the tests
If you like to run the tests, just open a terminal in the project directory and run:
python -m unittest discover -s test -p "*_test.py"
Built With
Contributing
First of all: Thank you very kindly for your interest in contributing to our code!
Please take a moment and read CONTRIBUTING.md to get you started!
Versioning
We use SemVer for versioning. For the versions available, see the releases on this repository.
License
This project is licensed under the Apache 2.0 License - see the LICENSE file for details
Code of Conduct
Everyone interacting in the ProjectSetup project’s codebases, issue trackers, chat rooms, and mailing lists is expected to follow the Code of Conduct.
Metadata
Release files for ProjectSetup 0.1.1
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 |
|---|---|---|---|---|
| ProjectSetup-0.1.1.tar.gz | 13.2 kB | Without provenance | Details for ProjectSetup-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ProjectSetup-0.1.1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for ProjectSetup-0.1.1-py2.py3-none-any.whl |
Total release size: 28.7 kB
Release files / ProjectSetup-0.1.1.tar.gz
| Download URL | ProjectSetup-0.1.1.tar.gz |
|---|---|
| Size | 13.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
500531440a598315ee4faf07e504c0ece5d627ca44a963d2193812073b4816b3
|
|
BLAKE2b-256 checksum How to use checksums |
dcdb5d59790fc6421983d42431173cd598ca563547fad76702f1d29ce672a389
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / ProjectSetup-0.1.1-py2.py3-none-any.whl
| Download URL | ProjectSetup-0.1.1-py2.py3-none-any.whl |
|---|---|
| Size | 15.5 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
9a95bee12013989bda509d9fc20535529327b622cc299e0c3e65117328a8d905
|
|
BLAKE2b-256 checksum How to use checksums |
7ebb47eabe39b4702b1c6b65bc6637d2401e24a521c8ad0729925315de52fcd4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ProjectSetup 0.1.1
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.