Skip to content

Removing pm4py from Prosimos #56

Open

Description

@iharsuvorau

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.

To deal with XES in general, we can:

  • assume logs come in CSV only
  • convert XES to CSV without pm4py

I started development of https://github.com/AutomatedProcessImprovement/openxes-cli-py. If it suits your needs give it a try or let me know in what cases it doesn't work for you.

Activity

  1. ira-halenok commented on Jun 29, 2023

    @ira-halenok
    Contributor

    @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:

    1. Prosimos where we deprecate XES format completely
    2. 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.

  2. iharsuvorau commented on Jul 27, 2023

    @iharsuvorau
    ContributorAuthor

    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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions