# Deleuze
A simple system for generating new python projects according to a resonable default skeleton. Example:
$ deleuze new supertool
This will generate the following project directory structure:
` supertool |-- bin | +-- supertool.py |-- reqs | +-- common.txt | +-- dev.txt | +-- production.txt | +-- test.txt |-- supertool | +-- __init__.py |-- tests | +-- __init__.py | +-- base.py | +-- factories.py | +-- test_supertool.py +-- README.md +-- requirements.txt +-- setup.py `
This provides, what is solely in my opinion, a decent initial project structure. The requirements files are preconfigured, reasonable testing defaults are added, and a failing unit-test is included in supertool/tests/test_supertool.py to remind you to start by writing some passing tests.
Next I usually spin up a new virtualenv environment for this project, install the requirements, and get to work on something more interesting.
1 maintainer
Metadata
1 maintainer
Release files for deleuze 0.9
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 |
|---|---|---|---|---|
| deleuze-0.9.tar.gz | 4.0 kB | Without provenance | Details for deleuze-0.9.tar.gz |
Release files / deleuze-0.9.tar.gz
| Download URL | deleuze-0.9.tar.gz |
|---|---|
| Size | 4.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ff9185158f883804f13a29d060ecc1735479a4aaa577a156ec2b248c36db6c71
|
|
BLAKE2b-256 checksum How to use checksums |
6b650100722b6d85eb8a504547eb39151cae32e58b783a88b42079364fb6488a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for deleuze 0.9
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.
