This release is a pre-release and may not be stable for production use.
pyworkflow
pyworkflow is a simple workflow platform used in scientific applications. It has been initially developed within the Scipion framework for image processing in Electron Microscopy.
pyworkflow allows you to define a working Domain by defining the following group of classes:
Objects: input/outputs that will be generated by different programs
Protocols: special type of Objects that have defined input parameters and will produce some output
Viewers: Entities that provide graphical analysis of results.
Wizards: Small GUIs that can be develop to help users to select given parameter values.
Development
We are now fully going toward Python 3!
To install pyworkflow for development purposes, one can do:
# Create a clean virtual environment
python -m venv ~/myenv
source ~/myenv/bin/activate
git clone git@github.com:scipion-em/scipion-pyworkflow.git
cd scipion-pyworkflow
python -m pip install -e . # Install in the environment as development
Running tests
First make sure that pyworkflow is available as a Python module in your current Python environment. During development, I tend to set the PYTHONPATH:
cd scipion-pyworkflow
# Either you have installed as mentioned above, or modify the PYTHONPATH
export PYTHONPATH=$PYTHONPATH:$PWD
# After pyworkflow is accesible as a module, then:
cd pyworkflow/tests
python -m unittest discover
# Simple project GUI can be shown after running tests:
cd scipion-pyworkflow
# At the moment you need to specify SCIPION_DOMAIN and SCIPION_VERSION
export SCIPION_DOMAIN=scipion-pyworkflow/pyworkflow/tests/mock_domain
export SCIPION_VERSION=3.0.0
python pyworkflow/apps/pw_project.py TestProtocolOutputs
Installation
Using a python virtual environment you might need: # For virtual env in ubuntu: # sudo apt-get install python3-dev # sudo apt-get install python3-tk
Metadata
Release files for scipion-pyworkflow 3.0.0a11
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 |
|---|---|---|---|---|
| scipion-pyworkflow-3.0.0a11.tar.gz | 1.0 MB | Without provenance | Details for scipion-pyworkflow-3.0.0a11.tar.gz |
Release files / scipion-pyworkflow-3.0.0a11.tar.gz
| Download URL | scipion-pyworkflow-3.0.0a11.tar.gz |
|---|---|
| Size | 1.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e6d69fb8154c8ee89580c3cf8f0015e6d9a3b1823a017f4019f07efecc78604b
|
|
BLAKE2b-256 checksum How to use checksums |
f67a96f2d92e6a9f482465c07e194f8a8864f0a6eb599485141d7f16d2803e2a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.46.1 CPython/3.8.3
|
Security for scipion-pyworkflow 3.0.0a11
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.