Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#13979 closed (worksforme)

Django manage.py doesn’t work with IPython

Reported by: ingo86 Owned by: nobody
Component: Core (Management commands) Version: 1.2
Severity: Keywords: manage.py shell ipython
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

I am on MacOSX Snow Leopard and I'm using python 2.6.5 installed with macports. I'm inside a virtualenv.
I can't run python manage.py shell after installing IPython but I can run IPython standalone.
I figured out that the following line, contained into IPython is what causes the issue:

(status, result) = commands.getstatusoutput( "otool -L %s | grep libedit" % _rl.__file__ )

This happens because for a strange reason, the method getstatusoutput is not available when i launch python manage.py shell but it's available when I launch ipython. I can import the commands module in both cases. I tried looking at the sys.path during the execution of both, but there are no differences.

Change History (4)

comment:1 Changed 5 years ago by adamnelson

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

iPython works fine for me with stock python 2.6.1 on Snow Leopard. I'm in a virtualenv.

readline is all jacked up on Mac/iPython (making the up arrow not work properly) - but there's a fix for that if you update readline explicitly.

Also, you should move to brew, macports is painful.

comment:2 Changed 5 years ago by mk

  • Component changed from Core framework to django-admin.py

I'm using IPython on Snow Leopard all the time. I think this ticket should be resolved as "worksforme".

comment:3 Changed 5 years ago by adamnelson

  • Resolution set to worksforme
  • Status changed from new to closed

Two people saying worksforme seems sufficient to mark it as such. Again, for future readers, the 'typical' Django installation on a Mac is:

  • Snow Leopard
  • Everything installed via homebrew
  • Use virtualenv for the environment
  • Use pip to install packages (i.e. everywhere somebody says "easy_install package_name", do "pip install package_name"

comment:4 Changed 5 years ago by russellm

@adamnelson: That's a common setup, but it's not universal. I, for one, don't use homebrew at all; all my databases and support libraries are native installs.

That said, I'm not seeing this problem either.

Note: See TracTickets for help on using tickets.
Back to Top