>
> This is one of the big differences between python and matlab: in matlab,
> if an m-file has changed within a session, the change is immediately
> effective. The python "import" statement is very different.
Gotchya, thanks.
So, while I'm being a bother:
in Matlab, I often organize data
On 2012/09/08 3:50 AM, Jody Klymak wrote:
> Ack, OK, to answer my own question...
>
> Somehow ipython was caching the definition of jmkfigure, so changing the
> module in the jmkfigure.py file did not actually change the version
> ipython was using. Running a new version of ipython, it worked fine.
Ack, OK, to answer my own question...
Somehow ipython was caching the definition of jmkfigure, so changing the module
in the jmkfigure.py file did not actually change the version ipython was using.
Running a new version of ipython, it worked fine.
Sorry for the chatter, and thanks for the poi
Hi all,
Thats what I thought too:
I have: jmkfigure.py:
===
from pylab import *
def jmkfigure():
rc('figure',figsize=(3+3/8,8.5/2),dpi=96)
rc('font',size=9);
===
and test.py:
=
from pylab import *
from jmkfigure import *
jmkfigure()
figure(1)
plot([1,2,3]
On 2012/09/07 7:52 PM, Paul Tremblay wrote:
> in your jmkfile.py you should have
>
> from pylab import *
Or to be more pythonic, import only what you actually need in a given
module, e.g.,
from matplotlib import rc
Eric
>
> Paul
>
>
>
> On 9/8/12 12:45 AM, Jody Klymak wrote:
>> Hi All,
>>
>
