have ipengine run start-up scripts before registering with the controller
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| IPython |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
This is late in the 0.10, but I am wondering can we get this feature in: being
able to launch ipengines with "ipengine -s initscript.py" so the ipengine
prepares itself before registering with the ipcontroller?
This suggestion comes from a previous "Won't Fix" bug:
https:/
>On Wed, Nov 21, 2008 at 6:38 PM, Brian Granger <email address hidden> wrote:
>> For my own engine initialization problem, I started to like the simple
>> method Ming proposed: to have engines run a script when they come up
>> and before they register to the controller, say, by launching the
>> engines with "ipengine -s initscript.py". However, I did not see an
>> apparent way to manage it. Maybe again I am missing something here?
>
>Can you submit a new bug report about this particular issue. It
>should work, but it doesn't! Also, this will be easy to fix!
-yichun
| Brian Granger (ellisonbg) wrote Re: [Bug 381386] [NEW] have ipengine run start-up scripts before registering with the controller | #1 |
| Changed in ipython: | |
| status: | New → Confirmed |
Yes, I think this is a good idea. As long as it happens before the
engines register with the controller.
Brian
On Thu, May 28, 2009 at 9:50 AM, yichun <email address hidden> wrote:
> Public bug reported:
>
> This is late in the 0.10, but I am wondering can we get this feature in: being
> able to launch ipengines with "ipengine -s initscript.py" so the ipengine
> prepares itself before registering with the ipcontroller?
>
> This suggestion comes from a previous "Won't Fix" bug:
> https:/
>
>>On Wed, Nov 21, 2008 at 6:38 PM, Brian Granger <email address hidden> wrote:
>>> For my own engine initialization problem, I started to like the simple
>>> method Ming proposed: to have engines run a script when they come up
>>> and before they register to the controller, say, by launching the
>>> engines with "ipengine -s initscript.py". However, I did not see an
>>> apparent way to manage it. Maybe again I am missing something here?
>>
>>Can you submit a new bug report about this particular issue. It
>>should work, but it doesn't! Also, this will be easy to fix!
>
> -yichun
>
> ** Affects: ipython
> Importance: Undecided
> Status: New
>
> --
> have ipengine run start-up scripts before registering with the controller
> https:/
> You received this bug notification because you are a member of IPython
> Developers, which is subscribed to IPython.
>
> Status in IPython - Enhanced Interactive Python: New
>
> Bug description:
> This is late in the 0.10, but I am wondering can we get this feature in: being
> able to launch ipengines with "ipengine -s initscript.py" so the ipengine
> prepares itself before registering with the ipcontroller?
>
> This suggestion comes from a previous "Won't Fix" bug:
> https:/
>
>>On Wed, Nov 21, 2008 at 6:38 PM, Brian Granger <email address hidden> wrote:
>>> For my own engine initialization problem, I started to like the simple
>>> method Ming proposed: to have engines run a script when they come up
>>> and before they register to the controller, say, by launching the
>>> engines with "ipengine -s initscript.py". However, I did not see an
>>> apparent way to manage it. Maybe again I am missing something here?
>>
>>Can you submit a new bug report about this particular issue. It
>>should work, but it doesn't! Also, this will be easy to fix!
>
> -yichun
>
--
Brian E. Granger, Ph.D.
Assistant Professor of Physics
Cal Poly State University, San Luis Obispo
<email address hidden>
<email address hidden>