PyBigDFT
PyBigDFT is a comprehensive Python package for driving, analyzing, and extending BigDFT electronic structure calculations. It provides tools for setting up simulations, parsing and post-processing results, and integrating BigDFT workflows with other Python-based scientific software.
Features
- High-level Python interface to BigDFT drivers and analysis tools
- Utilities for atom, molecule, and fragment manipulation
- Database and file format interoperability
- Scripting and automation support for BigDFT workflows
- Extensible framework for custom analysis and integration
Installation
You can install PyBigDFT and its dependencies using pip:
pip install .
Documentation
Full documentation is available at: https://www.bigdft.org/
Contributing
Contributions, bug reports, and feature requests are welcome. Please open an issue or submit a pull request on the project's repository.
Versioning
PyBigDFT follows a unique versioning system. The MAJOR.MINOR.PATCH sections of the version mirror that of the current BigDFT release.
This is supplemented by an incrementing version number that represents the version of PyBigDFT over this milestone.
For example, if you are working with BigDFT 1.9.6, you would use PyBigDFT==1.9.6.x, where x is the actual patch number of PyBigDFT.
Version compatibility may exist outside of this system, but development will focus on ensuring compatibility between matching versions.
Automatic Versioning
There is configuration for the bumpver tool present in pyproject.toml.
You can automatically increment the PyBigDFT version by running:
bumpver update
This will update the version number in the necessary locations.
Force the BigDFT portion of the version number to update with:
bumpver update --major, bumpver update --minor, or bumpver update --patch
License
PyBigDFT is distributed under the GNU General Public License (GPL).
Metadata
Release files for PyBigDFT 1.9.6.1
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 | |
|---|---|---|---|---|
| pybigdft-1.9.6.1.tar.gz | 305.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pybigdft-1.9.6.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 772.7 kB
Release files / pybigdft-1.9.6.1.tar.gz
| Download URL | pybigdft-1.9.6.1.tar.gz |
|---|---|
| Size | 305.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
039fac7f6ac9083680a31f9eb1319d53b2ef23e4aca2212fe97c72317135d846
|
|
BLAKE2b-256 checksum How to use checksums |
8252b7ade8409e1165b6a20ba6741323ccdb299449934804b02ffa8baf3e5cae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.16
|
Release files / pybigdft-1.9.6.1-py3-none-any.whl
| Download URL | pybigdft-1.9.6.1-py3-none-any.whl |
|---|---|
| Size | 467.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d9d4fee7bdd12ec1b9496d7c5712e45adbf52fdb68feeba406c7e0f01917ddb3
|
|
BLAKE2b-256 checksum How to use checksums |
2c9e5a18c8cc046980dc8bc276d1a03ffd7725926dab9e97ef54667df6f09b9e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.16
|
Security for PyBigDFT 1.9.6.1
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.