This library provides a set of pre-built tasks for your, pynt based, build.py along with supporting utility and project specific functions.
Install
pip install pynt-of-django
Usage
From within your build.py, setup pyntofdjango.
import os import pyntofdjango pyntofdjango.setup_pod(os.path.abspath(__file__))
Import any tasks you may need. See pyntofdjango’s build.py for a full list.
from pyntofdjango.tasks import create_venv, manage, test_nose
Now you should see your new tasks on the command line.
pynt -l
Additional Tools
You are likely to run into cases that the canned tasks don’t cover. Or maybe they are close but not exactly what you want. For this the lower level functions may be useful when building your own pynt tasks.
There is a project module containing functions specific to your project.
from pyntofdjango import project
As well as a utils module containing general utility functions.
from pyntofdjango import utils
About
This project builds on the basic way to use virtualenv, where the virtualenv folder (called venv) is placed within the project and ignored by the repo.
Why an in-project virtualenv?
The most important bit is that it allows devs to get going with your project without worrying about virtualenv all the time. There are more reasons and there are disadvantages. Christopher Webber has an explitive filled presentation on some of the reasons in-project virtualenvs may be your style.
Why not use [my favorite build tool]?
Pynt is very simple but nice for that same reason.
It’s pure Python and as a result it works great on all platforms.
It’s only a local build tool and not a deployment tool and neither is this project.
It supports Python 3 and so does this project.
It makes for a cool companion project name.
History
0.3.2 (2018-02-09)
Removed Django installation requirement
0.3.1 (2018-02-09)
Fixed issue with manage.py being found in .tox
0.3.0 (2015-08-07)
Most commands wrapping an underlying executable now accept both positional and named (–foo=bar) shell arguments.
create_venv now uses –no-site-packages for venv by default
test_tox is working again
clean works again, also cross platform compliant
Now using pyntcontrib functions where possible
0.2.0 (2015-02-01)
test_* and manage related tasks now pass along args to underlying commands.
For safety: delete_venv task now refuses to delete a dir larger than a max of ~500mb
0.1.0 (2014-11-16)
First release on PyPI.
Metadata
Release files for pynt-of-django 0.3.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 | Actions |
|---|---|---|---|---|
| pynt-of-django-0.3.2.tar.gz | 12.9 kB | Without provenance | Details for pynt-of-django-0.3.2.tar.gz |
Release files / pynt-of-django-0.3.2.tar.gz
| Download URL | pynt-of-django-0.3.2.tar.gz |
|---|---|
| Size | 12.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1f46212fd2912485aa0f416ff238036769426d1adc47279c641bd85ef0666635
|
|
BLAKE2b-256 checksum How to use checksums |
4038b32e8b0122b2fffea0771a1fdc53bb81312bff5f7dcac7bcefdde7c59ed6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pynt-of-django 0.3.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.