For yet another option, if you are a zc.buildout user[1], and include a python interpreter 'part' (the sample below provides `bin/py`), I found simply adding 'bpython' to the eggs will generate the `bin/ bpython` script, with the same pre configured sys.path, providing easy interaction with just your project code and any build dependencies.

Minimal buildout configuration sample [buildout.cfg] for 'my_project':

{{{
[buildout]
develop = .
parts = python

[python]
recipe = zc.recipe.egg
interpreter = py
eggs = bpython
     my_project
}}}

Thanks for the bpython recommendation, a very welcome enhancement!

Paul

[1]  http://www.buildout.org/

On Nov 23, 2010, at 1:49 PM, Mike Orr wrote:

If you're using Ubuntu 10.10, the "python-setuptools" is Distribute,
and it's working well. "python-virtualenv" and "virtualenvwrapper" are
also recent versions -- I don't have to install them manually anymore.

--Mike

On Tue, Nov 23, 2010 at 1:10 PM, Leo Shklovskii <[email protected]> wrote:
Strongly agree. Only use easy_install to install pip and forget it from
there.

Or just use Pete's plan :-)

--
--Leo

Pete wrote:

Step 0: use distribute instead of setuptools (basically a fork with fixes
- setuptools maintainer is... yeah).

http://pypi.python.org/pypi/distribute

Step 0.5: use pip (install logs, uninstall support, etc).

http://pypi.python.org/pypi/pip

--------
Dunno what's up with your particular install - I moved from macports to
fink about a year ago...

On Nov 20, 2010, at 7:48 PM, David Dyck wrote:


On Sat, Nov 20, 2010 at 7:12 AM, Pete <[email protected]
<mailto:[email protected]>> wrote:

   While we're on the subject of shells, IPython fans might like
   bpython. Autocompletion, highlighting, inline help (docstring
   display), logging... and that's more or less it.  Much simpler
   than IPython (which does a *lot* of other things, including
   distributed computing).

   http://bpython-interpreter.org/

   Bpython: It's the shell I always wished IPython would be.


Pete - thanks for this link - you'll never know the journey you enabled
:-)

Got the latest macports for macosx from http://www.macports.org/
Upgraded to python3.1   ( learning a bit about the changes between
python2.7 and 3.1 )
Investigated system tools "otool -L", "dtrace", Learned about Pygments (
syntax highlighting package written in Python )
Got so much useful information from Wikipedia that I send in a
contribution of gratitude ...

Downloaded and installed Colloguy where I found the helpful folks on
 #bpython on irc.freenode.net <http://irc.freenode.net/>

Learned about and started using pastebin for the first time (
http://bpaste.net/ ) ( found useful information on "Easy Install"
http://peak.telecommunity.com/DevCenter/EasyInstall and Python Eggs
 http://peak.telecommunity.com/DevCenter/PythonEggs )

But if anyone has some ideas why bpython doesn't install itself (or a
link) in a place
where it can be found in a reasonable path like python does - I'd sure
like to know.

  http://bpaste.net/show/11380/

Thanks,
  David





--
Mike Orr <[email protected]>

Reply via email to