-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DTT1 - Iteration 3 - WorkFlow engine module - Install module as Python lib #4909
Comments
UpdateResearching how to convert the python script to an installable library. Done:
Research about whether the library should be public in the pip repository should be discussed and in case the result is positive, the user needs to be defined. After this, it should be fully tested. Waiting for definitions. Moved to on hold. |
UpdateThere were changes in the test structure, so the libraries will be modified. Initially, the focus was solely on generating packages from the workflow. However, after a meeting with @fcaffieri and @QU3B1M , it has been decided that: There should be the possibility to install:
Some additional research is required to fulfill the new requirement |
Update
It is possible to create dependencies for each module all in one moving through directories. There is not an elegant solution to create the modules I want selecting it from the command line, unless it is mediated by script.
After knowing the performance and use of 'poetry', the decision is make only a library of workflow_engine
|
UpdateThe requested changes have been made. |
UpdateLaunchers .py will be renamed main.py and will be located each in each modules/{module} |
UpdateTesting performed
|
LGTM! |
ReviewGJ, a little change #4925 (comment) |
UpdateRequested changes done. |
LGTM |
Description
The objective of this issue is to allow the Workflow engine module to be installable as a python library so that it can be used as needed.
Taks
The text was updated successfully, but these errors were encountered: