Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #37547 > unrolled thread

The best, friendly and easy use Python Editor.

Back to article view | Back to comp.lang.python

Contents

  The best, friendly and easy use Python Editor. Hazard Seventyfour <hseventyfour@gmail.com> - 2013-01-24 01:43 -0800
    Re: The best, friendly and easy use Python Editor. mikprog@gmail.com - 2013-01-24 02:34 -0800
      Re: The best, friendly and easy use Python Editor. Miki Tebeka <miki.tebeka@gmail.com> - 2013-01-25 06:18 -0800
    Re: The best, friendly and easy use Python Editor. Chris Angelico <rosuav@gmail.com> - 2013-01-24 22:10 +1100
      Re: The best, friendly and easy use Python Editor. Walter Hurry <walterhurry@lavabit.com> - 2013-01-24 19:18 +0000
        RE: The best, friendly and easy use Python Editor. "Leonard, Arah" <Arah.Leonard@bruker-axs.com> - 2013-01-24 19:34 +0000
        Re: The best, friendly and easy use Python Editor. Dave Hirschfeld <dave.hirschfeld@gmail.com> - 2013-01-24 20:01 +0000
        Re: The best, friendly and easy use Python Editor. Tim Chase <python.list@tim.thechases.com> - 2013-01-24 14:25 -0600
        RE: The best, friendly and easy use Python Editor. "Leonard, Arah" <Arah.Leonard@bruker-axs.com> - 2013-01-24 20:32 +0000
        Re: The best, friendly and easy use Python Editor. Chris Angelico <rosuav@gmail.com> - 2013-01-25 10:29 +1100
        Re: The best, friendly and easy use Python Editor. Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-01-25 09:12 +0000
        RE: The best, friendly and easy use Python Editor. "Leonard, Arah" <Arah.Leonard@bruker-axs.com> - 2013-01-25 17:35 +0000
          Re: The best, friendly and easy use Python Editor. Neil Cerutti <neilc@norwich.edu> - 2013-01-25 17:54 +0000
            Re: The best, friendly and easy use Python Editor. Dave Angel <davea@davea.name> - 2013-01-25 13:12 -0500
          Re: The best, friendly and easy use Python Editor. rusi <rustompmody@gmail.com> - 2013-01-29 10:01 -0800
        Re: The best, friendly and easy use Python Editor. Chris Angelico <rosuav@gmail.com> - 2013-01-26 04:42 +1100
        Re: The best, friendly and easy use Python Editor. Wayne Werner <wayne@waynewerner.com> - 2013-01-31 07:34 -0600
    Re: The best, friendly and easy use Python Editor. John Gordon <gordon@panix.com> - 2013-01-24 15:12 +0000
      Re: The best, friendly and easy use Python Editor. Sharwan Joram <sharwan.joram@gmail.com> - 2013-01-24 07:37 -0800
        Re: The best, friendly and easy use Python Editor. John Gordon <gordon@panix.com> - 2013-01-24 15:51 +0000
          Re: The best, friendly and easy use Python Editor. Neil Cerutti <neilc@norwich.edu> - 2013-01-24 20:04 +0000
          Re: The best, friendly and easy use Python Editor. Tetsuya <io@noi.com> - 2013-01-24 22:14 +0100
            Re: The best, friendly and easy use Python Editor. Michael Torrie <torriem@gmail.com> - 2013-01-25 10:47 -0700
              Re: The best, friendly and easy use Python Editor. Tetsuya <io@noi.com> - 2013-01-25 23:03 +0100
    Re: The best, friendly and easy use Python Editor. rusi <rustompmody@gmail.com> - 2013-01-24 07:54 -0800
      Re: The best, friendly and easy use Python Editor. Chris Angelico <rosuav@gmail.com> - 2013-01-25 03:01 +1100
      Re: The best, friendly and easy use Python Editor. Thomas Heller <theller@ctypes.org> - 2013-01-24 17:23 +0100
        Re: The best, friendly and easy use Python Editor. Tim Chase <python.list@tim.thechases.com> - 2013-01-24 11:01 -0600
          Re: The best, friendly and easy use Python Editor. Neil Cerutti <neilc@norwich.edu> - 2013-01-24 20:06 +0000
      Re: The best, friendly and easy use Python Editor. llanitedave <llanitedave@veawb.coop> - 2013-01-24 13:09 -0800
        Re: The best, friendly and easy use Python Editor. Kayode Odeyemi <dreyemi@gmail.com> - 2013-01-24 22:24 +0100
    Re: The best, friendly and easy use Python Editor. Andrew Gudovich <andgudovich@gmail.com> - 2013-01-24 09:18 -0800
      Re: The best, friendly and easy use Python Editor. Kirill Pekarov <kpekarov@gmail.com> - 2013-01-25 01:43 -0800
        Re: The best, friendly and easy use Python Editor. Ritchie Flick <xenplex@gmail.com> - 2013-01-25 15:06 +0100
    Re: The best, friendly and easy use Python Editor. Wolfgang Keller <feliphil@gmx.net> - 2013-01-25 17:24 +0100

Page 1 of 2  [1] 2  Next page →

#37547 — The best, friendly and easy use Python Editor.

Hello,

I new in this python and decided to learn more about it, so i can make an own script :),

for all senior can you suggest me the best, friendly and easy use with nice GUI editor for me, and have many a good features such as auto complete/auto correct.

any recommend? Thanks ^_^

[toc] | [next] | [standalone]

#37552

On Thursday, January 24, 2013 9:43:31 AM UTC, Hazard Seventyfour wrote:
> Hello,
> 
> 
> 
> I new in this python and decided to learn more about it, so i can make an own script :),
> 
> 
> 
> for all senior can you suggest me the best, friendly and easy use with nice GUI editor for me, and have many a good features such as auto complete/auto correct.
> 
> 
> 
> any recommend? Thanks ^_^

Hi,
an editor is pretty much a matter of personal preferences.
I personally like Eclipse as I use it for most of my projects (not only Python) so I use Eclipse + PyDev plug-in for Python.

mik

[toc] | [prev] | [next] | [standalone]

#37669

On Thursday, January 24, 2013 2:34:45 AM UTC-8, mik...@gmail.com wrote:
> On Thursday, January 24, 2013 9:43:31 AM UTC, Hazard Seventyfour wrote:
> > for all senior can you suggest me the best, friendly and easy use with nice GUI editor for me, and have many a good features such as auto complete/auto correct.
> I personally like Eclipse as I use it for most of my projects (not only Python) so I use Eclipse + PyDev plug-in for Python.
Aptana is doing a great job bundling Eclipse + PyDev (+ other goodies).

[toc] | [prev] | [next] | [standalone]

#37562

On Thu, Jan 24, 2013 at 8:43 PM, Hazard Seventyfour
<hseventyfour@gmail.com> wrote:
> Hello,
>
> I new in this python and decided to learn more about it, so i can make an own script :),
>
> for all senior can you suggest me the best, friendly and easy use with nice GUI editor for me, and have many a good features such as auto complete/auto correct.
>
> any recommend? Thanks ^_^

Here we go, it's holy war time again! :)

You'll get a HUGE lot of responses. Many use emacs or vim, and you'll
get a few recommendations for IDLE. After that, it's a huge field of
options. I personally use SciTE; it's a good editor, but I don't
particularly like the way the project is run (nothing strong, but I
didn't like the tone on its mailing list). Eclipse has its fans, too.

A Python IDE is not nearly as beneficial as, say, a Java IDE. A good
Python editor just needs to do the basics like indentation, syntax
highlighting, and such; I like IDLE's method info when I'm working
interactively, but it's not a big deal when I'm writing a program. In
fact, all you really need out of an IDE can probably be supplied by
just a good editor, maybe a makefile, and alt-tabbing to IDLE.
However, if you want an IDE, they do exist.

ChrisA

[toc] | [prev] | [next] | [standalone]

#37620

On Thu, 24 Jan 2013 22:10:21 +1100, Chris Angelico wrote:

> On Thu, Jan 24, 2013 at 8:43 PM, Hazard Seventyfour
> <hseventyfour@gmail.com> wrote:
>> Hello,
>>
>> I new in this python and decided to learn more about it, so i can make
>> an own script :),
>>
>> for all senior can you suggest me the best, friendly and easy use with
>> nice GUI editor for me, and have many a good features such as auto
>> complete/auto correct.
>>
>> any recommend? Thanks ^_^
> 
> Here we go, it's holy war time again! :)
> 
> You'll get a HUGE lot of responses. Many use emacs or vim, and you'll
> get a few recommendations for IDLE. After that, it's a huge field of
> options. I personally use SciTE; it's a good editor, but I don't
> particularly like the way the project is run (nothing strong, but I
> didn't like the tone on its mailing list). Eclipse has its fans, too.
> 
> A Python IDE is not nearly as beneficial as, say, a Java IDE. A good
> Python editor just needs to do the basics like indentation, syntax
> highlighting, and such; I like IDLE's method info when I'm working
> interactively, but it's not a big deal when I'm writing a program. In
> fact, all you really need out of an IDE can probably be supplied by just
> a good editor, maybe a makefile, and alt-tabbing to IDLE. However, if
> you want an IDE, they do exist.

All true (especially the holy wars bit!). OP didn't (as far as I can see) 
even say which OS he is using. Anyway, my suggestion is generally that 
people use the editor with which they are already comfortable.

[toc] | [prev] | [next] | [standalone]

#37622

> All true (especially the holy wars bit!). OP didn't (as far as I can see) even say which OS he is using. Anyway, my suggestion is generally that people use the editor with which they are already comfortable.
> 

Sound advice.  Most of the time I still use Visual Studio for editing Python because I also use it for C++, so it's just what I'm used to.  No big deal, really.  Whatever works is what works.  It's just a text file after all.

[toc] | [prev] | [next] | [standalone]

#37624

Leonard, Arah <Arah.Leonard <at> bruker-axs.com> writes:

> 
> > All true (especially the holy wars bit!). OP didn't (as far as I can see) 
> >even say which OS he is using.
> Anyway, my suggestion is generally that people use the editor with which 
> > they are already comfortable.
> > 
> 
> Sound advice.  Most of the time I still use Visual Studio for editing Python 
> because I also use it for C++, so
> it's just what I'm used to.  No big deal, really.  Whatever works is what 
> works. It's just a text file after all.
> 

I assume you're using PyTools (http://pytools.codeplex.com/)?

-Dave

[toc] | [prev] | [next] | [standalone]

#37627

On 01/24/13 13:34, Leonard, Arah wrote:
>> All true (especially the holy wars bit!). OP didn't (as far as
>> I can see) even say which OS he is using. Anyway, my suggestion
>> is generally that people use the editor with which they are
>> already comfortable.
>
> Sound advice.  [snip] Whatever works is what works. It's just a
> text file after all.

So even "ed" or "edlin" or even "cat" would do ;-)
?
-tkc
?
wq

[toc] | [prev] | [next] | [standalone]

#37628

>> Sound advice.  Most of the time I still use Visual Studio for editing 
>> Python because I also use it for C++, so it's just what I'm used to.  
>> No big deal, really.  Whatever works is what works. It's just a text 
>> file after all.
>> 
> 
> I assume you're using PyTools (http://pytools.codeplex.com/)?
> 

Would that I could!  To my knowledge they still haven't backported PyTools to VS2008, which I'm presently stuck on because Python 2.7 still doesn't compile on VS2010.  :(

Kind of makes you think...

[toc] | [prev] | [next] | [standalone]

#37641

On Fri, Jan 25, 2013 at 7:25 AM, Tim Chase
<python.list@tim.thechases.com> wrote:
> On 01/24/13 13:34, Leonard, Arah wrote:
>>>
>>> All true (especially the holy wars bit!). OP didn't (as far as
>>> I can see) even say which OS he is using. Anyway, my suggestion
>>> is generally that people use the editor with which they are
>>> already comfortable.
>>
>>
>> Sound advice.  [snip] Whatever works is what works. It's just a
>> text file after all.
>
>
> So even "ed" or "edlin" or even "cat" would do ;-)

Definitely. Especially if your edlin syntax highlights Python.

ChrisA

[toc] | [prev] | [next] | [standalone]

#37655

On 24/01/2013 19:34, Leonard, Arah wrote:
>
> It's just a text file after all.
>

True indeed, let's not worry about trivial issues like indentation, 
mixing tabs and spaces or whatever.  Notepad anybody? :)

-- 
Cheers.

Mark Lawrence

[toc] | [prev] | [next] | [standalone]

#37681

>>
>> It's just a text file after all.
>>
> 
> True indeed, let's not worry about trivial issues like indentation, mixing tabs and spaces or whatever.  Notepad anybody? :)
> 

Hey, I didn't say Notepad was the *best* tool for the job, just that Python scripts are merely text files.

Though, that said, I have used Notepad and Wordpad any number of times in the past to edit Python files, all without bringing the universe to an untimely end.  Even used DOS Edit once.  You use what you have at the time.  A good craftsman never blames the tools.  ;)

[toc] | [prev] | [next] | [standalone]

#37685

On 2013-01-25, Leonard, Arah <Arah.Leonard@bruker-axs.com> wrote:
> Though, that said, I have used Notepad and Wordpad any number
> of times in the past to edit Python files, all without bringing
> the universe to an untimely end.  Even used DOS Edit once.  You
> use what you have at the time.  A good craftsman never blames
> the tools.  ;)

DOS Edit was great for quick edits. The file size limit is a
pity, though.

-- 
Neil Cerutti

[toc] | [prev] | [next] | [standalone]

#37686

On 01/25/2013 12:54 PM, Neil Cerutti wrote:
> On 2013-01-25, Leonard, Arah <Arah.Leonard@bruker-axs.com> wrote:
>> Though, that said, I have used Notepad and Wordpad any number
>> of times in the past to edit Python files, all without bringing
>> the universe to an untimely end.  Even used DOS Edit once.  You
>> use what you have at the time.  A good craftsman never blames
>> the tools.  ;)
>
> DOS Edit was great for quick edits. The file size limit is a
> pity, though.
>

I once had to write a text editor that would run in a 32k machine 
without a disk drive.  The editor had to fit in RAM with the data, so 
the text files were limited to 320 lines.

-- 
DaveA

[toc] | [prev] | [next] | [standalone]

#37893

On Jan 25, 10:35 pm, "Leonard, Arah" <Arah.Leon...@bruker-axs.com>
wrote:
> >> It's just a text file after all.
>
> > True indeed, let's not worry about trivial issues like indentation, mixing tabs and spaces or whatever.  Notepad anybody? :)
>
> Hey, I didn't say Notepad was the *best* tool for the job, just that Python scripts are merely
> text files.

"text files" ok. "Merely text files" needs some rebuttal
http://blog.languager.org/2012/10/html-is-why-mess-in-programming-syntax.html
Yeah its a bit tongue-in-cheek and does not directly answer the OP (to
which anyway I said: interpreter is more important than editor)

[toc] | [prev] | [next] | [standalone]

#37683

On Sat, Jan 26, 2013 at 4:35 AM, Leonard, Arah
<Arah.Leonard@bruker-axs.com> wrote:
>>>
>>> It's just a text file after all.
>>>
>>
>> True indeed, let's not worry about trivial issues like indentation, mixing tabs and spaces or whatever.  Notepad anybody? :)
>>
>
> Hey, I didn't say Notepad was the *best* tool for the job, just that Python scripts are merely text files.
>
> Though, that said, I have used Notepad and Wordpad any number of times in the past to edit Python files, all without bringing the universe to an untimely end.  Even used DOS Edit once.  You use what you have at the time.  A good craftsman never blames the tools.  ;)

I've edited files using any number of poor tools, but that doesn't
mean I'd choose them for daily work. Blame your tools no, but choose
which ones you carry around on your belt. I have a couple of
special-purpose editors that absolutely *suck* for general work, but
have a specific feature that makes them good for one particular
situation... one editor has a 32KB limit, no spiffy features, and
sometimes mishandles line endings, but it edits files on my remote
server, and can sometimes work when SSHing isn't an option. But
there's no way I'd use that for any other purpose than remote editing.

ChrisA

[toc] | [prev] | [next] | [standalone]

#37991

On Thu, 24 Jan 2013, Tim Chase wrote:

> On 01/24/13 13:34, Leonard, Arah wrote:
>>> All true (especially the holy wars bit!). OP didn't (as far as
>>> I can see) even say which OS he is using. Anyway, my suggestion
>>> is generally that people use the editor with which they are
>>> already comfortable.
>> 
>> Sound advice.  [snip] Whatever works is what works. It's just a
>> text file after all.
>
> So even "ed" or "edlin" or even "cat" would do ;-)
> ?
> -tkc
> ?
> wq

ed *is* the standard editor.

Also, I see what you did there ;)

-w
.
wq

[toc] | [prev] | [next] | [standalone]

#37596

In <a7c3d4a0-3277-428b-8cfc-c52ea585ba2f@googlegroups.com> Hazard Seventyfour <hseventyfour@gmail.com> writes:

> Hello,

> I new in this python and decided to learn more about it, so i can make
> an own script :),

> for all senior can you suggest me the best, friendly and easy use with
> nice GUI editor for me, and have many a good features such as auto
> complete/auto correct.

Try PyScripter.

http://code.google.com/p/pyscripter/

-- 
John Gordon                   A is for Amy, who fell down the stairs
gordon@panix.com              B is for Basil, assaulted by bears
                                -- Edward Gorey, "The Gashlycrumb Tinies"

[toc] | [prev] | [next] | [standalone]

#37600

On Thursday, January 24, 2013 8:42:19 PM UTC+5:30, John Gordon wrote:
> In <a7c3d4a0-3277-428b-8cfc-c52ea585ba2f@googlegroups.com> Hazard Seventyfour <hseventyfour@gmail.com> writes:
> 
> 
> 
> > Hello,
> 
> 
> 
> > I new in this python and decided to learn more about it, so i can make
> 
> > an own script :),
> 
> 
> 
> > for all senior can you suggest me the best, friendly and easy use with
> 
> > nice GUI editor for me, and have many a good features such as auto
> 
> > complete/auto correct.
> 
> 
> 
> Try PyScripter.
> 
> 
> 
> http://code.google.com/p/pyscripter/
> 
> 
> 
> -- 
> 
> John Gordon                   A is for Amy, who fell down the stairs
> 
> gordon@panix.com              B is for Basil, assaulted by bears
> 
>                                 -- Edward Gorey, "The Gashlycrumb Tinies"

use vim.

~Sharwan Joram

[toc] | [prev] | [next] | [standalone]

#37602

In <ccf57220-4367-4611-b91b-5bf2a51e3fa2@googlegroups.com> Sharwan Joram <sharwan.joram@gmail.com> writes:

> use vim.

He said he wanted autocomplete.  Does Vim have that?

-- 
John Gordon                   A is for Amy, who fell down the stairs
gordon@panix.com              B is for Basil, assaulted by bears
                                -- Edward Gorey, "The Gashlycrumb Tinies"

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | comp.lang.python

csiph-web