ipython should be used as default shell in remote_api_shell [35888460]

Feature Request

Status Update

No update yet.

Description

jm...@gmail.com

created issue #1

Nov 22, 2010 03:51AM

It would be convenient if ipython was used as the default shell for remote_api_shell. However, the user should still be able to fall back to the standard python shell if the --plain option is used.

The code in the attached patch is similar to what's found in the shell_plus django-command-extension:

http://code.google.com/p/django-command-extensions/source/browse/trunk/django_extensions/management/commands/shell_plus.py?r=135

ipython.patch

1.7 KB

View

Download

Comments

jm...@gmail.com <jm...@gmail.com> #2Nov 22, 2010 04:04AM

[Comment deleted]

ipython.patch

1.7 KB

View

Download

jo...@google.com <jo...@google.com> Sep 14, 2011 12:47AM

Assigned to jo...@google.com.

al...@gmail.com <al...@gmail.com> #3Jul 13, 2012 04:50PM

Would you be able to provide an example app which produces an error for which gcloud doesn't report, but appcfg.py does?

remote_api_shell.py

4.7 KB

View

Download

[Deleted User] <[Deleted User]> #4Jan 11, 2014 04:15AM

In this case it is not app specific, The 400 error is due to quota of the application versions being over the limit which is 10 (but for this specific project it has been increased to 60). So any project with more than 10 versions will experience this.

pv...@google.com <pv...@google.com> #5Oct 28, 2014 05:14PM

[Comment deleted]

br...@gmail.com <br...@gmail.com> #6Oct 28, 2014 05:38PM

I have forwarded this request/report to the engineering team. We will update this issue with any progress updates and a resolution.

pv...@google.com <pv...@google.com> #7Nov 24, 2014 05:49PM

I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.

Best regards, pvoutsinas

is...@google.com <is...@google.com> May 10, 2018 06:14PM

Status: New

Issue 35888460

Description

Issue summary

Comments

jm...@gmail.com <jm...@gmail.com> #2Nov 22, 2010 04:04AM

jo...@google.com <jo...@google.com> Sep 14, 2011 12:47AM

al...@gmail.com <al...@gmail.com> #3Jul 13, 2012 04:50PM

[Deleted User] <[Deleted User]> #4Jan 11, 2014 04:15AM

pv...@google.com <pv...@google.com> #5Oct 28, 2014 05:14PM

br...@gmail.com <br...@gmail.com> #6Oct 28, 2014 05:38PM

pv...@google.com <pv...@google.com> #7Nov 24, 2014 05:49PM

is...@google.com <is...@google.com> May 10, 2018 06:14PM

Add comment

Issue metadata