Skip to content

Migration Strategy / What about python libraries? #2

@skatenerd

Description

@skatenerd

I'm really excited about this project. I just started imagining what it would be like to incrementally migrate to Purescript, but I'm a little bit confused.

Suppose I have a big Python project and I want to migrate a single module from Python to Purescript. If this module depends on a handful of other Python libraries I guess there are two options:

  1. Replace those library calls with calls to Purescript libs
  2. Somehow call the Python libs from the new Purescript code

Both of these options seem a little weird.

Option 1 breaks down if your Python module depends on other Python modules in the same project; it forces you to implement your migration "bottom up". This option also requires us to be able to transpile arbitrary Purescript libs to Python, which might not wind up being supported.

Option 2 is also a bit weird because you're essentially doing FFI which will mark a lot of your values as "impure".

Were you picturing Option 2? I wouldn't be surprised if there are other approaches that I don't see.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions