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

Django 2 and Python 3 support #117

Merged
merged 21 commits into from
Jul 1, 2019
Merged

Django 2 and Python 3 support #117

merged 21 commits into from
Jul 1, 2019

Conversation

rnegron
Copy link
Contributor

@rnegron rnegron commented Jun 22, 2019

General Changelog

Added

  • Python 3.7 support
  • Django 2.2 support
  • Pipenv support

Changed

  • Updated most packages to latest version
  • Replaced pycrypto with pycryptodome
  • Use Django's built-in libmemcached instead of third-party
  • Replaced django-states with django-fsm
  • Alter code to be Python 3 and Django 2 compliant
  • Adopt black code style

@rnegron
Copy link
Contributor Author

rnegron commented Jun 30, 2019

Replacing django-states (no support for Python 3) with django-fsm is tricky... Opted to modify migration file, and include a squashed migration... Easiest solution is obviously to delete/overwrite existing meeting data.

Any better ideas?

@rnegron rnegron marked this pull request as ready for review June 30, 2019 16:33
@gcollazo
Copy link
Contributor

gcollazo commented Jul 1, 2019

@rnegron tienes deploy rights en Heroku. Be my guest.

@rnegron rnegron merged commit ecd0897 into master Jul 1, 2019
@rnegron rnegron deleted the django-2-and-python-3 branch July 1, 2019 23:08
@rnegron rnegron mentioned this pull request Jul 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants