[IPython-user] IPython1 0.3 prerelease

Pettit, Keith (SAIC) Keith.Pettit@bp....
Tue May 13 12:24:06 CDT 2008


It seemed to work for me.  I had succesfully installed a previous dev
version a month ago though.  Here is my system and test results.

OS: RHEL4u6
ARCH: AMD64
Install method: easy_install ipython1
Trial ipython1 results:
  Ran 300 tests in 19.982s
  PASSED (successes=300)

Do you have any other tests that you might want me to run?  I do a lot
of SGE cluster stuff if there is any parallel type tests that would be
fun to try.

When is ipython1 going to replace ipython?  It would be nice to start
adding the ipython features to ipython1.

Thanks,

Keith
 



-----Original Message-----
From: ipython-user-bounces@scipy.org
[mailto:ipython-user-bounces@scipy.org] On Behalf Of
ipython-user-request@scipy.org
Sent: Tuesday, May 13, 2008 12:00 PM
To: ipython-user@scipy.org
Subject: IPython-user Digest, Vol 55, Issue 8

Send IPython-user mailing list submissions to
	ipython-user@scipy.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.ipython.scipy.org/mailman/listinfo/ipython-user
or, via email, send a message with subject or body 'help' to
	ipython-user-request@scipy.org

You can reach the person managing the list at
	ipython-user-owner@scipy.org

When replying, please edit your Subject line so it is more specific than
"Re: Contents of IPython-user digest..."


Today's Topics:

   1. IPython1 0.3 prerelease (Brian Granger)
   2. Re: IPython1 0.3 prerelease (Paul Moore)
   3. Re: OS X: symbolic links, module paths,	logging module
      (Ville M. Vainio)
   4. Re: OS X: symbolic links, module paths,	logging module
      ( Jussi Rasinm?ki )


----------------------------------------------------------------------

Message: 1
Date: Mon, 12 May 2008 21:05:55 -0600
From: "Brian Granger" <ellisonbg.net@gmail.com>
Subject: [IPython-user] IPython1 0.3 prerelease
To: "ipython-dev Mailing list" <ipython-dev@scipy.org>, 	"ipython
user
	list" <ipython-user@scipy.org>
Message-ID:
	<6ce0ac130805122005td861b88uda3f2067b571d5ab@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

Hi,

We are getting ready to release version 0.3 of IPython1.  This version
has been long in the waiting and has lots of new features and
enhancement.  Trying IPython1 out is easier than ever, as it is
easy_installable now (don't worry, we still have a plain distutils
setup.py as well):

easy_install ipython1

This will get the latest ipython1 0.3 prerelease as well as Twisted and
zope.interface if you don't have it.  Please try installing this
prerelease and running the test suite (trial ipython1).  The final
version of ipython1 0.3 will be cut later this week.

For the curious, here are the list of changes:


New features
------------

	* Much improved ``setup.py`` and ``setupegg.py`` scripts.
Because Twisted
	  and zope.interface are now easy installable, we can declare
them as dependencies
	  in our setupegg.py script.
	* IPython1 is now compatible with Twisted 2.5.0 and 8.x.
	* Added a new example of how to use
:mod:`ipython1.kernel.asynclient`.
	* Initial draft of a process daemon in :mod:`ipython1.daemon`.
	* The ``TaskController`` now has methods for getting the queue
status.
	* The ``TaskResult`` objects not have information about how long
the task
	  took to run.
	* We are attaching additional attributes to exceptions
``(_ipython_*)`` that
	  we use to carry additional info around.
	* New top-level module :mod:`asynclient` that has asynchronous
versions (that
	  return deferreds) of the client classes.  This is designed to
users who want
	  to run their own Twisted reactor
	* All the clients in :mod:`client` are now based on Twisted.
This is done by
	  running the Twisted reactor in a separate thread and using the
	  :func:`blockingCallFromThread` function that is in recent
versions of Twisted.
	* Functions can now be pushed/pulled to/from engines using
	  :meth:`MultiEngineClient.push_function` and
:meth:`MultiEngineClient.pull_function`.
	* Gather/scatter are now implemented in the client to reduce the
work load
	  of the controller and improve performance.
	* Complete rewrite of the IPython1 docuementation.  All of the
documentation
	  from the IPython1 website has been moved into docs/source as
restructured
	  text documents.  PDF and HTML documentation are being
generated using
	  Sphinx.
	* New developer oriented documentation: development guidelines
and roadmap.
	* Traditional ``ChangeLog`` has been changed to a more useful
``changes.txt`` file
	  that is organized by release and is meant to provide something
more relevant
	  for users.

Bug fixes
---------

	* Created a proper ``MANIFEST.in`` file to create source
distributions.
	* Fixed a bug in the ``MultiEngine`` interface.  Previously,
multi-engine
	  actions were being collected with a :class:`DeferredList` with
	  ``fireononeerrback=1``.  This meant that methods were
returning
	  before all engines had given their results.  This was causing
extremely odd
	  bugs in certain cases. To fix this problem, we have 1) set
	  ``fireononeerrback=0`` to make sure all results (or
exceptions) are in
	  before returning and 2) introduced a :exc:`CompositeError`
exception
	  that wraps all of the engine exceptions.  This is a huge
change as it means
	  that users will have to catch :exc:`CompositeError` rather
than the actual
	  exception.

Backwards incompatible changes
------------------------------

	* All names have been renamed to conform to the
lowercase_with_underscore
	  convention.  This will require users to change references to
all names like
	  ``queueStatus`` to ``queue_status``.
	* Previously, methods like :meth:`MultiEngineClient.push` and

	  :meth:`MultiEngineClient.push` used ``*args`` and
``**kwargs``.  This was
	  becoming a problem as we weren't able to introduce new keyword
arguments into
	  the API.  Now these methods simple take a dict or sequence.
This has also allowed
	  us to get rid of the ``*All`` methods like :meth:`pushAll` and
:meth:`pullAll`.
	  These things are now handled with the ``targets`` keyword
argument that defaults
	  to ``'all'``.
	* The :attr:`MultiEngineClient.magicTargets` has been renamed to
	  :attr:`MultiEngineClient.targets`.
	* All methods in the MultiEngine interface now accept the
optional keyword argument
	  ``block``.
	* Renamed :class:`RemoteController` to
:class:`MultiEngineClient` and
	  :class:`TaskController` to :class:`TaskClient`.
	* Renamed the top-level module from :mod:`api` to :mod:`client`.
	* Most methods in the multiengine interface now raise a
:exc:`CompositeError` exception
	  that wraps the user's exceptions, rather than just raising the
raw user's exception.
	* Changed the ``setupNS`` and ``resultNames`` in the ``Task``
class to ``push``
	  and ``pull``.

Cheers,

Brian


------------------------------

Message: 2
Date: Tue, 13 May 2008 08:36:46 +0100
From: "Paul Moore" <p.f.moore@gmail.com>
Subject: Re: [IPython-user] IPython1 0.3 prerelease
To: "Brian Granger" <ellisonbg.net@gmail.com>
Cc: ipython user list <ipython-user@scipy.org>,	ipython-dev Mailing
	list <ipython-dev@scipy.org>
Message-ID:
	<79990c6b0805130036y406f5134i483bc512cc0a9f2a@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

2008/5/13 Brian Granger <ellisonbg.net@gmail.com>:
>  We are getting ready to release version 0.3 of IPython1.  This 
> version  has been long in the waiting and has lots of new features and

> enhancement.  Trying IPython1 out is easier than ever, as it is  
> easy_installable now (don't worry, we still have a plain distutils  
> setup.py as well):
>
>  easy_install ipython1
>
>  This will get the latest ipython1 0.3 prerelease as well as Twisted  
> and zope.interface if you don't have it.  Please try installing this  
> prerelease and running the test suite (trial ipython1).  The final  
> version of ipython1 0.3 will be cut later this week.

Given that I don't use eggs, can I check - are Twisted and
zope.interface now mandatory prerequisites? They certainly weren't in
the previous version. Also, I assume that on Windows, pyreadline is
still needed?

Paul.


------------------------------

Message: 3
Date: Tue, 13 May 2008 12:05:37 +0300
From: "Ville M. Vainio" <vivainio@gmail.com>
Subject: Re: [IPython-user] OS X: symbolic links, module paths,
	logging module
To: " Jussi Rasinm?ki " <jussi.rasinmaki@simosol.fi>
Cc: ipython-user@scipy.org
Message-ID:
	<46cb515a0805130205i21051c4eh9ac8634ab6f02e54@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

On Mon, May 12, 2008 at 8:49 AM, Jussi Rasinm?ki
<jussi.rasinmaki@simosol.fi> wrote:

>  1) I use symbolic links as shortcuts to my script from data  folders 
> on Mac. First I %ran the script from IPython from the first  data 
> folder, then decided to switch to a different folder (and delete  the 
> symbolic link in the first folder), %cd to the other one and again  
> %run the script. The script has a bug, and the Traceback's filepath  
> for the script is  the one for the first run using the already deleted

> symbolic link.
>  I guess this is the reason why I don't seem to be able to set 
> breakpoints  for the module in pdb. This persists even after
restarting ipython.
>  How do I fix this?

I have no clue at this point. Certainly restarting ipython should fix
this...

>  2) The script uses the logging module to log messages. The  
> successive %runs within IPython result in multiple console log  
> messages. On the second run each message shows up twice on the screen,

> on the third run three time etc. Fix for this?

Ty reload(logging). You probably set up multiple loggers in the logging
module global space, and the old ones don't disappear between %run:s.

--
Ville M. Vainio - vivainio.googlepages.com
blog=360.yahoo.com/villevainio - g[mail | talk]='vivainio'


------------------------------

Message: 4
Date: Tue, 13 May 2008 13:31:02 +0300
From: " Jussi Rasinm?ki " <jussi.rasinmaki@simosol.fi>
Subject: Re: [IPython-user] OS X: symbolic links, module paths,
	logging module
To: "Ville M. Vainio" <vivainio@gmail.com>
Cc: ipython-user@scipy.org
Message-ID:
	<f674190e0805130331n6edfe9dev5064e6aab620d21f@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

>  >  1) I use symbolic links as shortcuts to my script from data
>  >  folders on Mac. First I %ran the script from IPython from the
first
>  >  data folder, then decided to switch to a different folder (and
delete
>  >  the symbolic link in the first folder), %cd to the other one and
again
>  >  %run the script. The script has a bug, and the Traceback's
filepath
>  >  for the script is  the one for the first run using the already
deleted
>  >  symbolic link.
>  >  I guess this is the reason why I don't seem to be able to set
breakpoints
>  >  for the module in pdb. This persists even after restarting
ipython.
>  >  How do I fix this?
>
>  I have no clue at this point. Certainly restarting ipython should fix
this...

This may actually have something to do with the fact that my Python
environment was something of a mess (Apple, python.org & Fink). I've
cleaned things up a little and am now running .org 2.5.2 and IPython
0.8.3.svn.r3001. There is still one problem though which might be
related to the one above:
Modifying the source externally using Textmate => %run =>
modifications aren't picked up by IPython & a new pyc isn't created
even if I remove the pyc manually (sometimes, sometimes removing pyc
works). The traceback does show the modified code though. Restarting
does fix this.

>  >  2) The script uses the logging module to log messages. The
>  >  successive %runs within IPython result in multiple console log
>  >  messages. On the second run each message shows up twice on the
screen,
>  >  on the third run three time etc. Fix for this?
>
>  Ty reload(logging). You probably set up multiple loggers in the
>  logging module global space, and the old ones don't disappear between
>  %run:s.

Spot on, thanks!

Jussi

>  --
>  Ville M. Vainio - vivainio.googlepages.com
>  blog=360.yahoo.com/villevainio - g[mail | talk]='vivainio'
>


------------------------------

_______________________________________________
IPython-user mailing list
IPython-user@scipy.org
http://lists.ipython.scipy.org/mailman/listinfo/ipython-user


End of IPython-user Digest, Vol 55, Issue 8
*******************************************


More information about the IPython-user mailing list