Custom Step
Description
A SEAMM plug-in for custom Python scripts in a flowchart.
This plug-in provides custom python scripting in flowcharts. The scripts have access to the variables in the flowchart, and can set them as well as get their values. The scripts can access all of the functionality in the SEAMM framework as well as other installed Python packages.
Free software: BSD license
Documentation: https://molssi-seamm.github.io/custom_step/index.html
Features
Read and write access to flowchart variables.
Access to the molecular system along with all of its methods.
Access to the tables in the flowchart.
Standard Python, including all installed packages.
Credits
This package was created with Cookiecutter and the molssi-seamm/cookiecutter-seamm-plugin project template.
Developed by the Molecular Sciences Software Institute (MolSSI), which receives funding from the National Science Foundation under award ACI-1547580
History
- 2026.3.15 – Improved error handling
Printing a traceback for errors in Python to both job.ou and to stderr.txt in the working directory.
- 2023.12.3 – Removed pinning for dependencies
Removed pinning for dependencies to allow for more flexibility in the versions of the dependencies that can be used.
Updated to new documentation, workflows, etc.
0.1.0 (13 February 2019)
First release on PyPI.
0.7.0 (17 December 2019)
Fixed a bug updating the display when hitting the Cancel button.
0.9 (15 April 2020)
Internal changes only: - Cleaned up the continuous integration scripts. - Cleaned up code and setup.
2020.12.4 (4 December 2020)
Echoing the first lines of the script to Job.out to help understand and document the run.
2021.2.10 (10 Feb 2021)
Updated the README file to give a better description.
Updated the short description in setup.py to work with the new installer.
Added keywords to better searchability.
1 maintainer
Metadata
1 maintainer
Release files for custom-step 2026.3.15
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 | |
|---|---|---|---|---|
| custom_step-2026.3.15.tar.gz | 288.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| custom_step-2026.3.15-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 309.0 kB
Release files / custom_step-2026.3.15.tar.gz
| Download URL | custom_step-2026.3.15.tar.gz |
|---|---|
| Size | 288.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f1a1901a4a1233252fb4b4f76422fecbb59b2c374582e54d0ea1becc98e04cbf
|
|
BLAKE2b-256 checksum How to use checksums |
aed07e4acb156fc4cac8c79748721334469c9569ffa122873218da7d856acf0c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Release files / custom_step-2026.3.15-py2.py3-none-any.whl
| Download URL | custom_step-2026.3.15-py2.py3-none-any.whl |
|---|---|
| Size | 20.7 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
7a97a15e2d12c3d19fd35acdb25828113dcb5667136e108a474f58952ebdc3e9
|
|
BLAKE2b-256 checksum How to use checksums |
859a249c430951c079b0a55aefcafa21bce2603f9888df497aa17cda680c82e4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Security for custom-step 2026.3.15
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.
