django-vitae
Django-Vitae is a CV generator that can be used with the Django web framework.
Many academics have trouble keeping CVs up to date. Django-Vitae was created to streamline this process. Django-Vitae allows users to make highly customizable curricula vitae for use on their websites. The application provides models for common entries on curricula vitae such as education, employment, publications, teaching, and service. Django-Vitae eliminates many of the repetitive tasks related to producing curricula vitae. The included templates provide a complete CV “out of the box”, but allows researchers who might be interested in customizing the format using Django templating language.
Django-Vitae uses semantic versioning. Though it aims to provide a complete suite to create a CV, the project does not been tested extensively (and you can contribute to that effort!) and pieces might still throw errors. See notes below for quirks and errors in usage that must be resolved.
Requirements
Django-Vitae is developed and tested in Python 3. It depends on several external packages (other than Django):
Markdown (makes pretty HTML with simple text entries)
citeproc-py (creates citations formatted according to desired CSL styles [not yet implemented])
citeproc-py-styles (adds library of CSL styles)
reportlab (creates PDFs on-the-fly)
Installation
From PyPI:
pip install django-vitae
For the latest development version:
git clone https://github.com/mikebader/django-vitae cd django-vitae python setup.py install
If you are new to Django, you may want to visit the Getting Started guide in the documentation.
Documentation
Incomplete documentation can be found in the docs/ directory and at http://djangocv.readthedocs.io/.
Testing
To test, you need to install the following packages:
Nose & django-nose (used for testing suite)
Coverage (used to document testing coverage)
pip install nose pip install django-nose pip install coverage
A test suite can be found in the tests/ directory. With Nose and Coverage installed, you may run the tests with runtests.py. From the django-vitae root directory:
./runtests.py
To test only a single model, you may use the flag --attr=<model_name> for the model (not implemented for all models). For example, to test books, you would use:
./runtests.py --attr=book
Metadata
Release files for django-vitae 0.1.0
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-vitae-0.1.0.tar.gz | 798.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_vitae-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 910.0 kB
Release files / django-vitae-0.1.0.tar.gz
| Download URL | django-vitae-0.1.0.tar.gz |
|---|---|
| Size | 798.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
afd3f506b246c3fd7feaaf1cb5223c24519125107c71930de28e4c953887612e
|
|
BLAKE2b-256 checksum How to use checksums |
62301c9bc3b3e0ee53c37fbd5965ceff9808824a11889308b3d8014bf06b09db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/40.4.1 requests-toolbelt/0.8.0 tqdm/4.26.0 CPython/3.6.5
|
Release files / django_vitae-0.1.0-py3-none-any.whl
| Download URL | django_vitae-0.1.0-py3-none-any.whl |
|---|---|
| Size | 111.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f677e85172d1667e932d6eb7d31960fa6e3d43ceae675b8fd0d25eeab54573cf
|
|
BLAKE2b-256 checksum How to use checksums |
1d6787f2e7b3731f10da2693535a2bbd6e61c7323173cb3ba56d11dac6e46ed2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/40.4.1 requests-toolbelt/0.8.0 tqdm/4.26.0 CPython/3.6.5
|
Security for django-vitae 0.1.0
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.