You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to remove pm4py dependency ASAP, because of the licensing issue and its underlying cvxopt dependency that cannot be easily installed, especially, after migrating pandas to v2+.
So, I'm starting removal of pm4py from Prosimos, until the tests pass and Simod can depend on Prosimos again. Please, help with your use cases for XES logs that I might miss.
@orlenyslp regarding this item, it still needs to be implemented.
I think we agreed to stop supporting XES format completely a while ago.
If we decide to proceed forward with deprecation, this would require changes in multiple places:
Prosimos where we deprecate XES format completely
in prosimos-frontend, validation should be changed. Right now, user is able to select following extensions: ".xes, .csv, application/zip". This should be adjusted.
Any other repos do not include XES usage, so do not require any changes.
Hi @orlenyslp, we're still waiting for this issue to be closed before moving on to the next version with Simod. Could you please provide the timeline for the issue?
Activity
Remove pm4py dependency, #56
Merge pull request #57 from AutomatedProcessImprovement/issue_56
Move pm4py closer to points of actual usage to avoid import error whe…
ira-halenok commentedon Jun 29, 2023
@orlenyslp regarding this item, it still needs to be implemented.
I think we agreed to stop supporting XES format completely a while ago.
If we decide to proceed forward with deprecation, this would require changes in multiple places:
Prosimoswhere we deprecate XES format completelyprosimos-frontend, validation should be changed. Right now, user is able to select following extensions: ".xes, .csv, application/zip". This should be adjusted.Any other repos do not include XES usage, so do not require any changes.
iharsuvorau commentedon Jul 27, 2023
Hi @orlenyslp, we're still waiting for this issue to be closed before moving on to the next version with Simod. Could you please provide the timeline for the issue?