Skip to content
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

Decide what to do about Python code #59

Open
5 tasks
mmmaaatttttt opened this issue Apr 30, 2021 · 0 comments
Open
5 tasks

Decide what to do about Python code #59

mmmaaatttttt opened this issue Apr 30, 2021 · 0 comments
Labels
backend question refactor Refactor of existing functionality

Comments

@mmmaaatttttt
Copy link
Collaborator

Problem description:

Related to #14 but different. The Python files in the models folder are Python2, old and in need of an update. Feels a bit strange to have Python files in here, but I'd be ok with an upgrade to Python3 or a re-implementation in node instead.

Suggested solution:

If we stay in python, we'll need to:

if we move to node, we'll need to

  • add cheerio as a dependency
  • migrate each file to JS

We should break this up into sub-issues, but not until we make a decision about JS vs Python.

@mmmaaatttttt mmmaaatttttt added refactor Refactor of existing functionality question backend labels Apr 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend question refactor Refactor of existing functionality
Projects
None yet
Development

No branches or pull requests

1 participant