Skip to main content

Postgkyl

pytest

This is the Postgkyl project. It is both Python library and command-line tool designed to provide unified access to Gkeyll data together with a broad variety of analytical and visualization tools.

Documentation

Full documentation of the Gkeyll project is available at ReadTheDocs.

Dependencies and Installation

Postgkyl requires the following packages:

Note that Posgkyl currently does not work with NumPy >= 2.0; the update is in the works. In addition, there are two optional dependencies:

ADIOS 2 is required for reading Gkeyll 2 bp output files and it is not needed when working only with gkylzero. pytest is required only for developers.

We strongly recommend creating a virtual Python environment for everybody working with more than one Python project (this includes even using both Postgkyl and Sphinx). The two recommended options are venv and mamba.

With venv, one can create the virtual environment with:

python -m venv /path/to/new/virtual/environments/pgkyl

then activate it with:

| bash/zsh | source <venv>/bin/activate | | fish | source <venv>/bin/activate.fish | | csh/tcsh | source <venv>/bin/activate.csh |

and deactivate with:

deactivate

With mamba, one can create the virtual environment with:

mamba create -n pgkyl

then activate with:

mamba activate pgkyl

and deactivate with:

mamba deactivate

Note that with mamba, one can also use the provided environment.yml file, which also includes dependency specifications:

mamba env create -f environment.yml

Installing Postgkyl

The Postgkyl itself is installed with pip.1 Developers and uses who want to have the most up-to-date version should install Postgkyl from the source code:

git clone git@github.com:ammarhakim/postgkyl.git
cd postgkyl
pip install -e .[adios,test]

Alternatively, Postgkyl can be installed directly from PyPI:

pip install -e postgkyl[adios,test]

Note that ADIOS2 is not available on PyPI for Mac OSX; therefore, Mac users who want to use it need to install the dependency from elsewhere, for example, using the above-mentioned mamba and then do not use the adios tag with pip.

Testing

Postgkyl utilizes pytest for testing. The tests can be called manually from the root Postgkyl directory simply by using:

pytest [-v]

Authors

The full list of authors can be found here.

License

See Gkyl License for usage conditions.

  1. This does not require any additional modifications of PYTHONPATH. If Postgkyl was used previously through PYTHONPATH, we strongly recommend removing the path to the Postgkyl repository from the variable. ↩

Metadata

Release files for postgkyl 1.7.6

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

Source distribution (sdist)

Source distribution for postgkyl 1.7.6
File Size Uploaded Provenance Actions
postgkyl-1.7.6.tar.gz 128.2 kB Without provenance Details for postgkyl-1.7.6.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for postgkyl 1.7.6
File Interpreter ABI Platform Actions
postgkyl-1.7.6-py3-none-any.whl Python 3 none any Details for postgkyl-1.7.6-py3-none-any.whl

Total release size: 289.7 kB

Release files / postgkyl-1.7.6.tar.gz

Download URL postgkyl-1.7.6.tar.gz
Size 128.2 kB
Tags Source
SHA-256 checksum
How to use checksums
db134c7fffa953b15b3880e85835b2dc645db4435fe6fcd06469f302475858f3
BLAKE2b-256 checksum
How to use checksums
72111062e642b36e3a3166734146d01e01551fe452fed7d3cce90497b0d6bb17
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.1.0 CPython/3.12.11

Release files / postgkyl-1.7.6-py3-none-any.whl

Download URL postgkyl-1.7.6-py3-none-any.whl
Size 161.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
bdff3bb58c1c3b56f03e8015b1389d844213622f2c2fd1d203197eded8ff2235
BLAKE2b-256 checksum
How to use checksums
3589689d74f8a9202f2177dd8e620d97750712977e3e6415a516fe37523f85d7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.1.0 CPython/3.12.11

Security for postgkyl 1.7.6

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.

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