-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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's 'shell' command should use the Python Interactive window #13027
Comments
I believe this would work if we set the (See here for more information: https://www.b-list.org/weblog/2007/sep/22/standalone-django-scripts/) |
@anthonykim1 curious of your thoughts on this and if this is something that could relate to your repl work. |
Thanks @eleanorjboyd @rchiodo Are there any specific reasons you wanted to use Python Interactive window and/or iPython? This would be helpful in thinking about what is needed in REPL rewrite that is happening #21707 and the native VS Code REPL experience towards the end of the rewrite. |
Oh so you could get intellisense and have the output like a notebook window. Here's a good demonstration of the django shell: https://www.nickmccullum.com/useful-features-django-shell/ It looks a lot like an IPython shell. |
Meaning you'd run python code to check how things look. |
Now we have intellisense via Native REPL, but it might still be helpful to merge this issue with #13027 since I assume there are some scripts and environment variables that are Django specific that we can set before launching each Native REPL session. Folks who were interested in this issue, please go ahead and upvote the referenced issue #13027 |
The tutorial for Django has this command:
It would be cool if this could use the interactive window instead (it opens an ipython kernel)
The text was updated successfully, but these errors were encountered: