Prev: zipimport (.pyd & .so) files.
Next: any issues with long running python apps?
From: geremy condra on 10 Jul 2010 08:13
On Sat, Jul 10, 2010 at 7:05 AM, Dani Valverde <dani.valverde(a)gmail.com> wrote:
> geremy condra wrote:
>>
>> On Sat, Jul 10, 2010 at 6:49 AM, Dani Valverde <dani.valverde(a)gmail.com>
>> wrote:
>>
>>>
>>> geremy condra wrote:
>>>
>>>>
>>>> On Fri, Jul 9, 2010 at 1:08 PM, Dani Valverde <dani.valverde(a)gmail.com>
>>>> wrote:
>>>>
>>>>
>>>>>
>>>>> Sorry, I forgot to mention that I am using Linux. In fact, my first
>>>>> test
>>>>> have been with gedit. Is there any way to directly run the Python code
>>>>> into
>>>>> the console?
>>>>>
>>>>>
>>>>
>>>> Gedit has a plugin that brings up a python intepreter.
>>>> Edit->Preferences->Plugins->python console I think.
>>>>
>>>> Geremy Condra
>>>>
>>>>
>>>>
>>>
>>> I have this plugin enabled, but I don't know how to send the code to the
>>> console...
>>>
>>
>> type it in?
>>
>> Geremy Condra
>>
>>
>
> It could be a solution. But I am used to work with gEdit using the R
> statistical programming language plugin, and I am able to send the code to
> console instead of typing it in.

Not sure how that works, but everything in gedit is accessible through
python, so it should be a snap to put together a plugin to do what you
want.

Geremy Condra
From: Tim Johnson on 13 Jul 2010 16:47
On 2010-07-10, Andreas Waldenburger <usenot(a)geekmail.INVALID> wrote:
> On Fri, 9 Jul 2010 16:49:20 +0000 (UTC) Grant Edwards
><invalid(a)invalid.invalid> wrote:
>
>> On 2010-07-09, Dani Valverde <dani.valverde(a)gmail.com> wrote:
>>
>> > I am new to python and pretty new to programming (I have some
>> > expertise wit R statistical programming language). I am just
>> > starting, so my questions may be a little bit stupid. Can anyone
>> > suggest a good editor for python?
>>
>> Emacs, Scite (has nice folding), Vim, Eclipse.
>>
> Great tips for a newbie.
>
> Not.
>
> Well, they might be, but chances are, they are overkill for people new
> to programming and will only alienate them (Scite may be an exception).
> Text editors are an acquired taste.

Emacs and Vim are very difficult to learn. Emacs more so than vim
(even with vim's modal style of editing IMHO). However, to suggest that
either might alienate someone new to programming presupposes some
metric on their ability to learn. Since I am not privy to that metric,
read on:

As linux programmer, I use vim for python, javascript, rebol and adhoc system
management and emacs for lispish programmer languages.

1)Most releases of vim (such as those available from ubuntu repositories)
are compiled with the python binary embedded. Thus one could customize
vim using python itself.
2)Emacs is itself a design environment based on the elisp programming
language and both of these.

The time spent on learning either of these could pay off in the long
run, *but it would be a long run*.

Vim and emacs are available for Windows.

When I programmed in Windows I used two different editors: Pythowin,
obviously coming with the python for windows distribution.
Pythonwin is great and very 'helpful'.

Boxer - a freeware programmer's editor, that has the best balance
of configurability and ease of use of any editor that I have used.
But it has been years since I used either.

--
Tim
tim at johnsons-web.com or akwebsoft.com
http://www.akwebsoft.com
First  |  Prev  | 
Pages: 1 2 3
Prev: zipimport (.pyd & .so) files.
Next: any issues with long running python apps?