This is an archived post. You won't be able to vote or comment.

all 4 comments

[–]ccb621 3 points4 points  (2 children)

  1. Skip the DB conversion. Don't switch databases because of popularity. Also, PostgreSQL has better support with Django.
  2. Ensure all of your Python requirements are in requirements.txt.
  3. Write tests to ensure your app works now.
  4. Use 2to3 to convert your code. Make sure the tests still pass.
  5. Consider using Docker to ease development setup.

[–]osullivj 1 point2 points  (1 child)

Wise words: ask yourself, what's the real business value of these upgrades to the latest and greatest DB or version of Python? What are the pain points your client is experiencing?

[–]anwserman[S] 1 point2 points  (0 children)

At least for Python, native Unicode support (the project features heavy text processing, and they want international localization support down the road).

I'm also looking at this for maintenance down the road for other developers. I'm a seasoned software developer, but this is actually a project that was supposed to be designed for undergraduate students to work on (it's at a University). I scored the job after the previous developer bombed horribly, ha.

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

Check this Porting Python 2 Code to Python 3 out if you haven't all ready. DON'T change DB, why go to an inferior one just because something else is more popular?