Registry / workflow / fitz
library0.0.1.dev2pypiunverified

Fitz is an extremely early development library (version 0.0.1.dev2) for managing complex workflows, particularly in the context of neuroimaging data analysis. It provides basic components like DAGs, Nodes, and Workflows. The project appears to be abandoned, with no active development for over two years.

pip install fitz
INSTALL
IMPORT
SIG · FITZ
F
fitz
workflowenv0.0.1.dev2
Install
18.2s avg
Import
Disk
400MB
Pass rate
10/ 10
Env Coverage10 / 10
glibc
3.93.13
musl
3.93.13
Install & Compatibility
Where this runs
tested against v0.0.1.dev2 · pip install
no network on importno background threads
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
musl
py 3.103.910 runs
installs and imports cleanly · install 0.0s · import 0.000s · 395.8MB
glibc
py 3.103.910 runs
installs and imports cleanly · install 18.2s · import 0.000s · 383MB
400MB installed
● package 400MB
Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

Workflow
from fitz.workflow import Workflow
Node
from fitz.node import Node
DAG
from fitz.dag import DAG

This quickstart demonstrates the basic structure of creating `Nodes` and `Workflows` with dependencies using the `fitz` library. Due to its abandoned and extremely early development status, this example is derived from internal tests and is primarily conceptual. Actual execution logic for nodes and workflows is not robustly defined or easily runnable without deeper dive into the source code.

import os # NOTE: This library is in an extremely early development stage (0.0.1.dev2) # and appears to be abandoned. The following example is derived from internal tests # and may not be functional or representative of a stable API. # It is NOT recommended for production use. from fitz.workflow import Workflow from fitz.node import Node from fitz.dag import DAG # Define simple nodes (tasks) class SimpleNode(Node): def __init__(self, name, func=None): super().__init__(name) self.func = func or (lambda: print(f"Executing {name}")) def execute(self): self.func() # Create nodes node_a = SimpleNode('A') node_b = SimpleNode('B') node_c = SimpleNode('C') # Create a workflow and add nodes workflow = Workflow('MyExampleWorkflow') workflow.add_node(node_a) workflow.add_node(node_b) workflow.add_node(node_c) # Define dependencies (A -> B, A -> C) workflow.add_edge(node_a, node_b) workflow.add_edge(node_a, node_c) print(f"Workflow '{workflow.name}' created with nodes: {[n.name for n in workflow.nodes]}") print(f"Edges: {workflow.dag.edges}") # Attempt to run the workflow (functionality is limited and untested for general use) # For a real run, you'd likely need more complex node logic and an executor. # The project's tests suggest running tasks, but no clear 'workflow.run()' method exists at this level. # This is purely illustrative of structure. print("\n--- Attempting to show node execution order (conceptual) ---") for node in workflow.dag.topological_sort(): print(f"Ready to execute: {node.name}") # node.execute() # Actual execution requires more setup than this quickstart provides
Debug
Known issues
breakingThis `fitz` package (PyPI slug `fitz`) is *not* the popular PDF library PyMuPDF. PyMuPDF users commonly import it as `import fitz` after `pip install pymupdf`. This `fitz` package is an unrelated, abandoned neuroimaging workflow library, leading to severe confusion and unexpected behavior if mistaken for PyMuPDF.
fix
If you intend to use the PDF library, install `pymupdf` with `pip install pymupdf` and then `import fitz` in your code. If you truly wish to use this specific workflow library, be aware of its distinct identity and abandoned status.
affects: All versions (0.0.1.dev2 and earlier)
breakingThis project is in an extremely early development stage (version 0.0.1.dev2) and appears to be abandoned, with no commits in over two years. Its APIs are highly unstable, largely undocumented, and subject to arbitrary change or removal without warning. It is not suitable for production use.
fix
Avoid using this package for any critical or long-term projects. Consider alternative, actively maintained workflow management libraries or specialized neuroimaging tools. If experimenting, proceed with extreme caution and assume the code may not work as expected or at all.
affects: All versions (0.0.1.dev2 and earlier)
gotchaThere is no formal documentation, active community, or official support for this package. Usage patterns must be derived directly from the GitHub repository's source code and test files, which may be incomplete, outdated, or difficult to interpret for general use cases.
fix
Refer directly to the GitHub repository (http://github.com/kastman/fitz) and inspect the `fitz` directory and `tests` folder for clues on how the library was intended to be used. Be prepared for a significant lack of clarity and functional examples.
affects: All versions
Errors
Common errors & fixes
AttributeError: module 'fitz' has no attribute 'open'
Attempting to use the `fitz` neuroimaging package as if it were the PyMuPDF library (which is commonly imported as `fitz`). This `fitz` package does not contain PDF-related functionality.
fix
If you intended to use a PDF library, install PyMuPDF (`pip install pymupdf`) and then `import fitz` from that package. If you meant this `fitz` package, this error confirms you're trying to use PyMuPDF functionality that does not exist here.
ModuleNotFoundError: No module named 'fitz'
The `fitz` package has not been installed in the current Python environment.
fix
Install the package using pip: `pip install fitz`.
AttributeError: module 'fitz.workflow' has no attribute 'Workflow'
The specific class or attribute you are trying to import (`Workflow` in this example) may not exist, has been renamed, or its import path has changed. Given the highly unstable and abandoned nature of this development package, API changes are common and undocumented.
fix
Inspect the project's source code on GitHub (e.g., `fitz/workflow.py`) to verify the exact class name and its availability. However, it is strongly recommended to avoid using this package due to its instability and lack of maintenance.
Upgrade
Version history
0.0.1.dev2latest on PyPI
Audit
Dependencies

No dependency data recorded yet.

Agent activity
12 hits · last 30 days
node
8
OpenAI (training)
1
Resources

No resource links recorded.

fitz — pip install fitz · libregistry