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 fitzVerified import paths — ran on the pinned version, not inferred.
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.
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.
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.
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.
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.
Install the package using pip: `pip install fitz`.
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.
No dependency data recorded yet.
No resource links recorded.