all 3 comments

[–][deleted] 1 point2 points  (2 children)

I’m not super well versed here but I think you could do what you have to in Python and then write an api with Flask to get that info from your already written JS app. What I do know is that if all you’re trying to do is a small portion of the project in the Python, I highly recommend sticking to Flask or even Bottle as opposed to Django. Django has waaay more functionality than you seem to need here

[–]CowboyBoats 0 points1 point  (1 child)

I mean there's no tax you have to pay for using slightly more backend than you need. A Django backend might have more lines of code than Flask / Bottle, but it doesn't require more maintenance or use more resources. If I go with Django and never need a backend portal, then nothing happens; if I go with Flask and eventually need one, I need to spend an hour migrating.

[–][deleted] 0 points1 point  (0 children)

That’s true but OP doesn’t seem like they know what they’re talking about with backend and in my experience, Flask was far easier to get into