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

Add support for Django 1.9 #1043

Closed
GaelGirodon opened this issue Dec 30, 2015 · 4 comments
Closed

Add support for Django 1.9 #1043

GaelGirodon opened this issue Dec 30, 2015 · 4 comments
Assignees
Milestone

Comments

@GaelGirodon
Copy link

Python Tools for Visual Studio seems to have some issues with the last version of Django (1.9) :

  • syncdb is deprecated in Django 1.9, so the Python context menu should now use new commands like migrate, makemigrations... (or better, it would be great to make them customizable depending on framework version we're using!)
Unknown command: 'syncdb'
Type 'manage.py help' for usage.
  • The "Django Web Project" template seems to generate parts of code using deprecated features in Django 1.9, it would be nice to refresh the templates or to associate each template with a version of the framework (it's not a good idea to start a new project with some features already deprecated in our code!)
  • It seems that Intellisense needs a little update to deal with new features

In any case, thanks for your great job, it's awesome to be able to use Visual Studio for other technolgies like Python, Node.JS and much more!

@Luis-Palacios
Copy link

+1

@Sehales
Copy link

Sehales commented Jan 7, 2016

Definitely +1 please add support for Django 1.9. Thx for your awesome work!

@zooba
Copy link
Member

zooba commented Jan 8, 2016

Yep, we've been slow at keeping Django support up to date as they make changes to the library. Ideally we'd contribute debugging functionality into Django rather than relying on implementation details (debugging templates no longer works since 1.8).

Depending on what work we get to do for PTVS 3.0, we may end up with a model that is much easier to update between releases. However, right now it's unlikely we'll get anything fixed before the next major release.

@GaelGirodon
Copy link
Author

If you plan to improve all this stuff in a next major release, it's perfect! It's better to wait and get something more efficient in the end!

@zooba zooba modified the milestone: 2.2.3 Jan 28, 2016
@zooba zooba self-assigned this Jan 28, 2016
zooba added a commit to zooba/PTVS that referenced this issue Jan 29, 2016
Started fixing template debugging
@zooba zooba closed this as completed Jan 30, 2016
zooba added a commit to zooba/PTVS that referenced this issue Feb 1, 2016
Started fixing template debugging
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants