PyGuymer3
This is a Python 3.X port of my Python 2.X module containing a bunch of random functions that I have written over the years. The documentation is on Read The Docs and the module is on PyPI.
You may browse the coverage report for running the unit tests.
Installation
To install PyGuymer3, run:
# To install the latest released version from PyPI:
pip install --user PyGuymer3
# To install the latest development version from GitHub:
pip install --user git+https://github.com/Guymer/PyGuymer3.git
... and everything should "just work".
Dependencies
PyGuymer3 requires the following Python modules to be installed and available in your PYTHONPATH:
Additionally, due to the dependency on my FORTRAN library, if you want to run the FORTRAN-based functions in the f90 sub-module then you will also require the following Python modules to be installed and available in your PYTHONPATH:
Similarly, PyGuymer3 requires the following binaries to be installed and available in your PATH:
dotexiftoolffmpegandffprobegifsiclegitjpegtranlsdvdmetaflacmp4fileoptipngtarxz
Notes
The Zen of Python
import this
To Do
- Read this good StackOverflow answer describing type-checking which also provides a quick summary on PEP 484 and PEP 3107.
Bugs
- This module has been created from my Python 2.X module using the utility
2to3. As such, there may be bugs in the code as most of it has not been tested since the port. If you find anything wrong then please raise a bug report on GitHub. - The function pyguymer3.geo.area() sometimes returns erroneous areas. This has been tracked down to the Shapely function shapely.ops.voronoi_diagram(): for certain inputs (often when a point within the shape is exactly
0.0) some of the parts of the Voronoi diagram are inverted. When it goes wrong it reliably goes wrong for those inputs. Below, the blue circle is the 1 km buffer around a point at(0.0°, 0.0°)and the orange wedges are the parts of the Voronoi diagram. Note that the orange wedges foriVoroPoly = 10andiVoroPoly = 31are inverted - they are the negative of what they are supposed to be. As a consequence, when the area of each orange wedge is calculated and summed the total is very wrong..
Metadata
Release files for PyGuymer3 0.0.12
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 | Actions |
|---|---|---|---|---|
| pyguymer3-0.0.12.tar.gz | 69.9 MB | With provenance | Details for pyguymer3-0.0.12.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyguymer3-0.0.12-py3-none-any.whl | Python 3 | none | any | Details for pyguymer3-0.0.12-py3-none-any.whl |
Total release size: 146.6 MB
Release files / pyguymer3-0.0.12.tar.gz
| Download URL | pyguymer3-0.0.12.tar.gz |
|---|---|
| Size | 69.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5dfb223de0d47cf833bedb3780b952a6d9246f387ca98a09b68b86a8f9f31d8b
|
|
BLAKE2b-256 checksum How to use checksums |
81c9b5415bcfac605f4038658d8407f71e7b0acd1005329189c7bc39d17746c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 16, 2025.
Transparency logRelease files / pyguymer3-0.0.12-py3-none-any.whl
| Download URL | pyguymer3-0.0.12-py3-none-any.whl |
|---|---|
| Size | 76.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e9a08b36de04a6e962a9f8c7faf0bf89fefbcf5b68341d76822a4fed8f998083
|
|
BLAKE2b-256 checksum How to use checksums |
e5b461a2dbfa1010cebc014ef4ab8545feafbe9aa40b23799d405e5f7a052688
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 16, 2025.
Transparency logSecurity for PyGuymer3 0.0.12
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for pyguymer3-0.0.12.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 16, 2025.
Transparency logA 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.