Django DAG
Django-dag is a small reusable app which implements a Directed Acyclic Graph.
Usage
Django-dag uses abstract base classes, to use it you must create your own concrete classes that inherit from Django-dag classes.
The dag_test app contains a simple example and a unit test to show you its usage.
Example:
class ConcreteNode(node_factory('ConcreteEdge')):
"""
Test node, adds just one field
"""
name = models.CharField(max_length = 32)
class ConcreteEdge(edge_factory(ConcreteNode, concrete = False)):
"""
Test edge, adds just one field
"""
name = models.CharField(max_length = 32, blank = True, null = True)
Tests
- Unit tests can be run with just django installed at the base directory by running
python manage.py test
1 maintainer
Metadata
1 maintainer
Release files for django-dag 1.4.3
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 | |
|---|---|---|---|---|
| django-dag-1.4.3.tar.gz | 6.1 kB | Without provenance | Details |
Release files / django-dag-1.4.3.tar.gz
| Download URL | django-dag-1.4.3.tar.gz |
|---|---|
| Size | 6.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e5b003c2352be3ec80f983efde4a848533685a4039d0f5ce2e558553a8109e81
|
|
BLAKE2b-256 checksum How to use checksums |
c97426cb5bcc6235f68e9792684e441874cd4d9dbc90bf0db7f78bc932bbeaac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/40.6.3 requests-toolbelt/0.9.1 tqdm/4.38.0 CPython/3.6.8
|
Security for django-dag 1.4.3
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.
