Skip to main content

🚀 Django Core Plus

Description

Django functional modules.

Installation

Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.

Usage

Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.

Support

Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.

Roadmap

If you have ideas for releases in the future, it is a good idea to list them in the README.

Test and Build

Todo

Contributing

State if you are open to contributions and what your requirements are for accepting them.

For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.

You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.

Authors and acknowledgment

Show your appreciation to those who have contributed to the project.

License

For open source projects, say how it is licensed.

Project status

If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

Metadata

Release files for django-coreplus 0.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for django-coreplus 0.4
File Size Uploaded Provenance Actions
django-coreplus-0.4.tar.gz 330.3 kB Without provenance Details for django-coreplus-0.4.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for django-coreplus 0.4
File Interpreter ABI Platform Actions
django_coreplus-0.4-py3-none-any.whl Python 3 none any Details for django_coreplus-0.4-py3-none-any.whl

Total release size: 728.8 kB

Release files / django-coreplus-0.4.tar.gz

Download URL django-coreplus-0.4.tar.gz
Size 330.3 kB
Tags Source
SHA-256 checksum
How to use checksums
8a5469bf78a394d89320b9d1961d97d61c97c4b819c6ddcb0dae030b99e15dec
BLAKE2b-256 checksum
How to use checksums
3b6b2232a0352258c060c04a2ed1596c58187fb271b23421a5475e076a8cbc63
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.2 CPython/3.8.15

Release files / django_coreplus-0.4-py3-none-any.whl

Download URL django_coreplus-0.4-py3-none-any.whl
Size 398.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4baef847cdab45659b37ebc4dea094e38d3b598ceb73076d5b05a9342c3678e5
BLAKE2b-256 checksum
How to use checksums
702456075f83d2f36561bb91e6fdf4fea53ea7a681e0948f8c03660202d2c8a0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.2 CPython/3.8.15

Security for django-coreplus 0.4

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.

Release history Release notifications | RSS feed

This release

0.4 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page