On Sun, Jul 26, 2009 at 22:51, limodou<[email protected]> wrote:
>
> On Mon, Jul 27, 2009 at 12:34 PM, Dick Moores<[email protected]> wrote:
>> On Sun, Jul 26, 2009 at 21:01, yin sun<[email protected]> wrote:
>>> preference->python-> setup python interpreter
>>
>> Yes, and then what? The attached image shows what I already have there.
>>
>> Dick
>>
>>> On Sun, Jul 26, 2009 at 9:17 PM, Dick Moores <[email protected]> wrote:
>>>>
>>>> On Sun, Jul 26, 2009 at 20:04, limodou <[email protected]> wrote:
>>>> >
>>>> > On Mon, Jul 27, 2009 at 10:26 AM, Dick Moores<[email protected]> wrote:
>>>> > > Sorry for the dumb question, but I've been away for a while, and have
>>>> > > forgotten some basic stuff. I've downloaded 2.6.2 and want to start
>>>> > > using it
>>>> > > with Ulipad. In Win XP I've changed environmental variables
>>>> > > appropriately, I
>>>> > > believe. However, Ulipad's shell window still indicates 2.5.1. Same
>>>> > > with
>>>> > > IDLE. But if I start Python at command line, I get 2.6.2.
>>>> > >
>>>> > > Advice, please?
>>>> > >
>>>> > > Thanks,
>>>> > >
>>>> > > Dick Moores
>>>> > >
>>>> >
>>>> > Did you use source version?
>>>>
>>>> I used Python 2.6.2 Windows installer (Windows binary -- does not
>>>> include source) from <http://www.python.org/download/>
>>>>
>>>> Dick
>>>
>>>
>>
>
> I mean ulipad source version, but not python source version. You
> should know 2 things:
>
> 1. When you run ulipad in source version, the shell window will be the
> same python version of executing ulipad.

Well, I just updated Ulipad to rev. 507 by svn, so I suppose I'm using
the source version?

> 2. Run python file menu item is different from shell window. It'll use
> the python interpreter which you set in Preference.

I'd like both the shell window and run Python (F5) to use Python
2.6.2. Please tell me what to do to enable this. For one, as I replied
to yin sun, I don't know how to set the interpreter in Preferences. I
again attach my Ulipad Interpreter Setup.

Dick

<<attachment: Ulipad_Interpreter_Setup.png>>

Reply via email to