Lou Pecora <[EMAIL PROTECTED]> wrote:
> Impressive, but YIKES, there ought to be a simpler way to do this. I
> think during the development phase editing and reloading would be very
> common and you'd want everything updated.
Sorry I missed this thread...
This is what I use which is easy an
Peter Otten <[EMAIL PROTECTED]> wrote:
> Alex Martelli wrote:
>
> > Michele Simionato <[EMAIL PROTECTED]> wrote:
> >
> >> You want this recipe from Michael Hudson:
> >>
> >> http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/160164
> >>
> >> "automatically upgrade class instances on
Alex Martelli wrote:
> Michele Simionato <[EMAIL PROTECTED]> wrote:
>
>> You want this recipe from Michael Hudson:
>>
>> http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/160164
>>
>> "automatically upgrade class instances on reload()"
>
> Note that the version in the printed Cookb
Thanks all for the responses. Extra kudos to Steve J and Michele S.
that cleared it up for me.
the context of my question comes from reading up on Lisp in "Loving
Lisp - the Savy Programmer's Secret Weapon",
http://www.markwatson.com/opencontent/lisp_lic.htm, where the author
described building up
Lou Pecora enlightened us with:
> Impressive, but YIKES, there ought to be a simpler way to do this.
> I think during the development phase editing and reloading would be
> very common and you'd want everything updated.
I hardly ever reload stuff manually during development. I write a
script, and
In article <[EMAIL PROTECTED]>,
"Michele Simionato" <[EMAIL PROTECTED]> wrote:
> You want this recipe from Michael Hudson:
>
> http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/160164
>
> "automatically upgrade class instances on reload()"
Impressive, but YIKES, there ought to be
Michele Simionato <[EMAIL PROTECTED]> wrote:
> You want this recipe from Michael Hudson:
>
> http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/160164
>
> "automatically upgrade class instances on reload()"
Note that the version in the printed Cookbook (2nd edition) was
substantially
I think reload should be preceded by import.
Example:
Online code modification: upon modifying and saving mytest.py issue on
the interactive shell:
>>>import mytest
>>>reload(mytest)
The shell should respond with "" (NOT:mytest.pyc)
Note that modules importing mytest should not
You want this recipe from Michael Hudson:
http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/160164
"automatically upgrade class instances on reload()"
--
http://mail.python.org/mailman/listinfo/python-list
> In both languages, you can start up the interactive interpreter
> ('python' and 'irb'), load source files and do stuff, like create
> objects and call their methods. When you want to change something, you
> can edit those same source files outside the environment and reload
> them from within the
dmh2000 wrote:
> I am experimenting with the interactive interpreter environments of
> Python and Ruby and I ran into what seems to be a fundamental
> difference. However I may be doing something wrong in Python. Please
> comment and correct me if I am wrong
>
> In both languages, you can start u
dmh2000 enlightened us with:
> When you want to change something, you can edit those same source
> files outside the environment and reload them from within the
> interactive environment. But, here is the difference: with Python,
> when you reload the source file (module in Python terms), it seems
dmh2000 wrote:
> I am experimenting with the interactive interpreter environments of
> Python and Ruby and I ran into what seems to be a fundamental
> difference. However I may be doing something wrong in Python. Please
> comment and correct me if I am wrong
>
> In both languages, you can start up
I am experimenting with the interactive interpreter environments of
Python and Ruby and I ran into what seems to be a fundamental
difference. However I may be doing something wrong in Python. Please
comment and correct me if I am wrong
In both languages, you can start up the interactive interprete
14 matches
Mail list logo
