[SciPy-dev] scipy cow and proc.py

[Virgilio, Vincent]

Hi Pearu,

I vote to put proc.py next to cpuinfo.py, for some mild consistency.

Thanks for the fix in CVS; I'll try it soon.

Vince

> -----Original Message-----
> From: scipy-dev-bounces at scipy.net
> [mailto:scipy-dev-bounces at scipy.net] On Behalf Of Pearu Peterson
> Sent: Wednesday, May 12, 2004 4:04 PM
> To: SciPy Developers List
> Subject: RE: [SciPy-dev] scipy cow and proc.py
>
>
>
>
> On Wed, 12 May 2004, Virgilio, Vincent wrote:
>
> > I dropped proc.py into scipy/Lib, deleted scipy/MANIFEST, the reran
> > python2.3 setup.py bdist_rpm --fix-python.
> >
> > The generated scipy rpm included proc.py, and installed it into the
> > correct location. I was able to import scipy.proc and use various
> > functions.
> >
> > It looks like a success.
>
> Ok, then we should add proc.py to scipy, though it is
> currently Linux-only
> module. Maybe the proper place for it would be in scipy_base or
> scipy_distutils (the latter has cpuinfo.py).
>
> > Unfortunately scipy.cow still hangs during cow.start(), even with a
> > machine list of local nodes/ports only. Hm, I had this working some
> > earlier today . . .
> >
> > Also, I'm having trouble with scipy in help; I type help(),
> then scipy,
> > and get the below traceback. I'm using the latest CVS.
>
> Fixed in CVS.
>
> Thanks,
> Pearu
>
> _______________________________________________
> Scipy-dev mailing list
> Scipy-dev at scipy.net
> http://www.scipy.net/mailman/listinfo/scipy-dev
>

************************************
This email and any files transmitted with it are proprietary and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email
in error please notify the sender. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of ITT Industries, Inc.
The recipient should check this email and any attachments for the presence of viruses. ITT Industries accepts no liability for any damage caused by any virus transmitted by this
email.
************************************