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

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

IDE for python

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

Contents

  IDE for python Sameer Rathoud <sameer.rathoud@gmail.com> - 2014-05-28 03:43 -0700
    Re: IDE for python Marko Rauhamaa <marko@pacujo.net> - 2014-05-28 13:50 +0300
      Re: IDE for python Greg Schroeder <gmschroeder@gmail.com> - 2014-05-28 18:46 +0700
        Re: IDE for python Sameer Rathoud <sameer.rathoud@gmail.com> - 2014-05-28 05:56 -0700
          Re: IDE for python Sameer Rathoud <sameer.rathoud@gmail.com> - 2014-05-28 06:01 -0700
            Re: IDE for python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-05-28 15:36 +0100
          Re: IDE for python Duncan Booth <duncan.booth@invalid.invalid> - 2014-05-29 08:09 +0000
            Re: IDE for python Duncan Booth <duncan.booth@invalid.invalid> - 2014-05-29 08:32 +0000
      Re: IDE for python Chris Angelico <rosuav@gmail.com> - 2014-05-28 22:55 +1000
        Re: IDE for python wxjmfauth@gmail.com - 2014-05-28 08:38 -0700
          Re: IDE for python Wolfgang Maier <wolfgang.maier@biologie.uni-freiburg.de> - 2014-06-02 07:28 +0000
          Re: IDE for python Tim Golden <mail@timgolden.me.uk> - 2014-06-02 09:15 +0100
          Re: IDE for python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-06-02 10:02 +0100
          Re: IDE for python Chris Angelico <rosuav@gmail.com> - 2014-06-02 19:15 +1000
          Re: IDE for python Wolfgang Maier <wolfgang.maier@biologie.uni-freiburg.de> - 2014-06-02 10:10 +0000
          Re: IDE for python Tim Golden <mail@timgolden.me.uk> - 2014-06-02 11:43 +0100
          Re: IDE for python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-06-02 13:11 +0100
      Re: IDE for python Greg Schroeder <gmschroeder@gmail.com> - 2014-05-29 08:13 +0700
      Programmer's text editor, for Python and everything else (was: IDE for python) Ben Finney <ben@benfinney.id.au> - 2014-05-29 12:51 +1000
    答复: IDE for python "cheng.li" <scrappedprince.li@gmail.com> - 2014-05-28 18:51 +0800
    Re: IDE for python alister <alister.nospam.ware@ntlworld.com> - 2014-05-28 11:03 +0000
    Re: IDE for python Mihamina Rakotomandimby <mihamina.rakotomandimby@rktmb.org> - 2014-05-28 13:51 +0300
      Re: IDE for python Sameer Rathoud <sameer.rathoud@gmail.com> - 2014-05-28 04:31 -0700
        Re: IDE for python Chris Angelico <rosuav@gmail.com> - 2014-05-28 22:00 +1000
        Re: IDE for python "prashanth B.G" <prash.bg@gmail.com> - 2014-05-28 17:41 +0530
        Re: IDE for python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-05-28 13:35 +0100
          Re: IDE for python Sameer Rathoud <sameer.rathoud@gmail.com> - 2014-05-28 06:27 -0700
        Re: IDE for python Joseph Martinot-Lagarde <joseph.martinot-lagarde@m4x.org> - 2014-06-04 02:12 +0200
    Re: IDE for python Chris Angelico <rosuav@gmail.com> - 2014-05-28 21:33 +1000
    Re: IDE for python Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-05-28 13:04 +0000
      Re: IDE for python "Rhodri James" <rhodri@wildebst.org.uk> - 2014-05-29 00:12 +0100
        Re: IDE for python Chris Angelico <rosuav@gmail.com> - 2014-05-29 18:02 +1000
    Re: IDE for python William Ray Wing <wrw@mac.com> - 2014-05-28 08:47 -0400
    Re: IDE for python Mark H Harris <harrismh777@gmail.com> - 2014-05-28 09:25 -0500
    Re: IDE for python Wolfgang Keller <feliphil@gmx.net> - 2014-05-28 18:24 +0200
      Re: IDE for python "Ernest Bonat, Ph.D." <ernest.bonat@gmail.com> - 2014-05-28 10:24 -0700
    Re: IDE for python Deb Wyatt <codemonkey@inbox.com> - 2014-05-28 09:39 -0800
    Re: IDE for python Rustom Mody <rustompmody@gmail.com> - 2014-05-28 12:10 -0700
    Re: IDE for python Ben Finney <ben@benfinney.id.au> - 2014-05-29 08:13 +1000
    Re: IDE for python Wolfgang Maier <wolfgang.maier@biologie.uni-freiburg.de> - 2014-05-29 11:41 +0200
    Re: IDE for python Terry Reedy <tjreedy@udel.edu> - 2014-05-29 12:39 -0400
      Re: IDE for python Paul Rudin <paul.nospam@rudin.co.uk> - 2014-05-29 17:44 +0100
        Re: IDE for python Mark H Harris <harrismh777@gmail.com> - 2014-05-29 15:11 -0500
          Re: IDE for python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-05-29 21:41 +0100
          Re: IDE for python alister <alister.nospam.ware@ntlworld.com> - 2014-05-30 12:23 +0000
        Re: IDE for python Rustom Mody <rustompmody@gmail.com> - 2014-05-30 05:53 -0700
          Re: IDE for python Marko Rauhamaa <marko@pacujo.net> - 2014-05-30 16:54 +0300
            Re: IDE for python Rustom Mody <rustompmody@gmail.com> - 2014-05-30 07:04 -0700
              Re: IDE for python wxjmfauth@gmail.com - 2014-05-30 08:06 -0700
                Re: IDE for python Rustom Mody <rustompmody@gmail.com> - 2014-05-30 09:15 -0700
                  Re: IDE for python Terry Reedy <tjreedy@udel.edu> - 2014-05-30 12:37 -0400
                    Re: IDE for python Rustom Mody <rustompmody@gmail.com> - 2014-05-30 09:40 -0700
                  Re: IDE for python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-05-30 17:38 +0100
                    Re: IDE for python Rustom Mody <rustompmody@gmail.com> - 2014-05-30 10:07 -0700
                      Re: IDE for python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-05-30 18:27 +0100
                      Re: IDE for python Rustom Mody <rustompmody@gmail.com> - 2014-05-31 18:48 -0700
                        Re: IDE for python wxjmfauth@gmail.com - 2014-06-01 00:38 -0700
                        Re: IDE for python Marko Rauhamaa <marko@pacujo.net> - 2014-06-01 10:58 +0300
                          Re: IDE for python Chris Angelico <rosuav@gmail.com> - 2014-06-01 18:31 +1000
                            Re: IDE for python Rustom Mody <rustompmody@gmail.com> - 2014-06-01 01:52 -0700
                            Re: IDE for python Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-06-01 09:06 +0000
                              Re: IDE for python Chris Angelico <rosuav@gmail.com> - 2014-06-01 19:59 +1000
                    Re: IDE for python wxjmfauth@gmail.com - 2014-05-31 01:46 -0700
                  Re: IDE for python wxjmfauth@gmail.com - 2014-05-30 10:17 -0700
                    Re: IDE for python Rustom Mody <rustompmody@gmail.com> - 2014-05-30 10:30 -0700
                      Re: IDE for python wxjmfauth@gmail.com - 2014-05-30 11:43 -0700
            Re: IDE for python Terry Reedy <tjreedy@udel.edu> - 2014-05-30 11:46 -0400
          Re: IDE for python "Rhodri James" <rhodri@wildebst.org.uk> - 2014-06-01 00:17 +0100
    Re: IDE for python Chris Angelico <rosuav@gmail.com> - 2014-05-30 02:51 +1000
    Re: IDE for python Terry Reedy <tjreedy@udel.edu> - 2014-05-29 16:45 -0400
    Re: IDE for python Ben Finney <ben@benfinney.id.au> - 2014-05-30 07:05 +1000
    Re: IDE for python Travis Griggs <travisgriggs@gmail.com> - 2014-05-29 15:40 -0700
      Re: IDE for python Andrea D'Amore <anddamNOALPASTICCIODICARNE+gruppi@brapi.net> - 2014-05-30 09:21 +0200
        Re: IDE for python Andrea D'Amore <anddamNOALPASTICCIODICARNE+gruppi@brapi.net> - 2014-05-30 11:04 +0200

Page 4 of 4 — ← Prev page 1 2 3 [4]

#72368

On Sun, 01 Jun 2014 18:31:09 +1000, Chris Angelico wrote:

> the better solution is to permit the full Unicode alphabet in
> identifiers...

I'm not entirely sure about that. Full Unicode support in identifiers 
such as URLs doesn't create a brand new vulnerability, but it does 
increase it from a fairly minor problem to something *much* harder to 
deal with. It's bad enough when somebody manages to fool you into going 
to (say) app1e.com instead of apple.com, without also being at risk from 
аррlе, аpрlе, арplе and аррle (to mention just a few). At least nobody 
can fake .com with .соm.

To put it another way:

py> аррlе = 23
py> apple = 42
py> assert аррlе == apple
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AssertionError



-- 
Steven

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

#72369

On Sun, Jun 1, 2014 at 7:06 PM, Steven D'Aprano
<steve+comp.lang.python@pearwood.info> wrote:
> On Sun, 01 Jun 2014 18:31:09 +1000, Chris Angelico wrote:
>
>> the better solution is to permit the full Unicode alphabet in
>> identifiers...
>
> I'm not entirely sure about that. Full Unicode support in identifiers
> such as URLs doesn't create a brand new vulnerability, but it does
> increase it from a fairly minor problem to something *much* harder to
> deal with. It's bad enough when somebody manages to fool you into going
> to (say) app1e.com instead of apple.com, without also being at risk from
> аррlе, аpрlе, арplе and аррle (to mention just a few). At least nobody
> can fake .com with .соm.
>
> To put it another way:
>
> py> аррlе = 23
> py> apple = 42
> py> assert аррlе == apple
> Traceback (most recent call last):
>   File "<stdin>", line 1, in <module>
> AssertionError

Yeah, that is a concern. But as you say, it's already possible to
confuse rn with m (in many fonts) and i/l/1, and (on a different
level) Foo, foo, _foo, _Foo, and FOO, or movement_Direction and
movement_direction. If you saw one of those in one part of a program
and another in another, you'd have to consume an annoying amount of
mindspace to keep them separate.

Note, incidentally, that I said "alphabet" rather than the entire
Unicode character set. I do *not* support the use of, for instance,
U+200B 'ZERO WIDTH SPACE' in identifiers, that's just stupid :)

ChrisA

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

#72330

Le vendredi 30 mai 2014 18:38:04 UTC+2, Mark Lawrence a écrit :
> On 30/05/2014 17:15, Rustom Mody wrote:
> 
> > On Friday, May 30, 2014 8:36:54 PM UTC+5:30, wxjm...@gmail.com wrote:
> 
> >
> 
> > It is now about time that we stop taking ASCII seriously!!
> 
> >
> 
> 
> 
> This can't happen in the Python world until there is a sensible approach 
> 
> to unicode.  Ah, but wait a minute, the ball was set rolling with Python 
> 
> 3.0.  Then came PEP 393 and the Flexible String Representation in Python 
> 
> 3.3 and some strings came down in size by a factor of 75% and in most 
> 
> cases it was faster.  Just what do some people want in life, jam on it?
> 
> 
> 
> -- 
> 
> My fellow Pythonistas, ask not what our language can do for you, ask 
> 
> what you can do for our language.
> 
> 
> 
> Mark Lawrence
> 
> 
> 
> ---
> 
> This email is free from viruses and malware because avast! Antivirus protection is active.
> 
> http://www.avast.com

========

A guy who is understanding unicode would not have even
spent its time in writing a PEP 393 proposal.

I skip the discussion(s) I read here and there about PDF.

Put this comment in relation with my Xe(La)TeX knowledge.

jmf

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

#72312

Le vendredi 30 mai 2014 18:15:09 UTC+2, Rustom Mody a écrit :
> On Friday, May 30, 2014 8:36:54 PM UTC+5:30, wxjm...@gmail.com wrote:
> 
> 
> 
> > Out of curiosity.
> 
> > Are you the Rusi Mody attempting to dive in Xe(La)TeX?
> 
> 
> 
> Yeah :-)
> 
> 
> 
> As my blog posts labelled unicode will indicate I am a fan of using
> 
> unicode in program source:
> 
> http://blog.languager.org/search/label/Unicode
> 
> 
> 
> Of course it is not exactly a coincidence that I used APL a bit in my
> 
> early days.  At that time it was great fun though we did not take it
> 
> seriously.*
> 
> 
> 
> It is now about time that we stop taking ASCII seriously!!
> 
> 
> 
> And for those who dont know xetex, its is really xɘtex – a pictorial
> 
> anagram if written as XƎTEX
> 
> 
> 
> However in all fairness I should say that I cannot seem to find my
> 
> way to that promised land yet:
> 
> - xetex does not quite work whereas pdflatex works smoothly
> 
> - mathjax is awesome however its firmly latex (not xetex) based
> 
> 
> 
> -------------------
> 
> * And the fact that there are recent implementations including web ones means its by no means dead:
> 
> http://baruchel.hd.free.fr/apps/apl/
> 

> which I think unicode aficionados will enjoy


=========

Ok, thanks for the answer.


"xetex does not quite work whereas pdflatex works smoothly"

?

jmf

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

#72314

On Friday, May 30, 2014 10:47:33 PM UTC+5:30, wxjm...@gmail.com wrote:
> =========

> Ok, thanks for the answer.

> "xetex does not quite work whereas pdflatex works smoothly"

> ?

Problem is a combination of
1. I am a somewhat clueless noob
2. xetex is emerging technology therefore changing fast and not stable

So when something does not work I dont know whether:
- its 1 (I am doing something silly)
- Or 2 (I have actually hit a bug)

I tried writing some small (hello-world) type text using unicode chars rather 
the old-fashioned \alpha type of locutions. It worked.
Added a bunch of more latex packages from apt.
It stopped working.

------------------------------
PS It would help all if you read
https://wiki.python.org/moin/GoogleGroupsPython
and dont double-space earlier mails.

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

#72315

Le vendredi 30 mai 2014 19:30:27 UTC+2, Rustom Mody a écrit :
> On Friday, May 30, 2014 10:47:33 PM UTC+5:30, wxjm...@gmail.com wrote:
> 
> > =========
> 
> 
> 
> > Ok, thanks for the answer.
> 
> 
> 
> > "xetex does not quite work whereas pdflatex works smoothly"
> 
> 
> 
> > ?
> 
> 
> 
> Problem is a combination of
> 
> 1. I am a somewhat clueless noob
> 
> 2. xetex is emerging technology therefore changing fast and not stable
> 
> 
> 
> So when something does not work I dont know whether:
> 
> - its 1 (I am doing something silly)
> 
> - Or 2 (I have actually hit a bug)
> 
> 
> 
> I tried writing some small (hello-world) type text using unicode chars rather 
> 
> the old-fashioned \alpha type of locutions. It worked.
> 
> Added a bunch of more latex packages from apt.
> 
> It stopped working.
> 
> 
> 
> ------------------------------
> 
> PS It would help all if you read
> 
> https://wiki.python.org/moin/GoogleGroupsPython
> 
> and dont double-space earlier mails.

========

It's not the place to discuss TeX here.
(I have actually 16 more or less complete "distros" on
my hd on Windows, all working very well. They are on
my hd, but all run from an usb stick as well!)

jmf

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

#72305

On 5/30/2014 9:54 AM, Marko Rauhamaa wrote:
> Rustom Mody <rustompmody@gmail.com>:
>
>>>> 3. Search unopened files (grep) for a string or re.
>>
>> How do you do this with emacs?
>> I find a menagerie of greppish commands -- rgrep, lgrep, grep-find etc
>
> To grep for a pattern in the directory of the active buffer:
>
>     M-x grep
>     Run grep (like this): grep -nH -e
>
> Complete the grep command:
>
>     Run grep (like this): grep -nH -e class *.py
>
> and hit ENTER. Feel free to modify the command from grep to egrep, for
> example. I often replace -e with -i.
>
> To grep for a pattern in any subdirectory:
>
>     M-x grep
>     Run grep (like this): grep -nH -r assert .
>
> or:
>
>     M-x grep-find
>     Run find (like this): find . -type f -exec grep -nH -e assert {} +
>
> Again, you can modify the command freely:
>
>     M-x grep-find
>     Run find (like this): find . -name '*.py' -exec grep -nH -e assert {} +

Thank you for the answer. I once had things like this memorized, but now 
I prefer Idle's dialog, with selected text (if any) and the full path of 
the current directory (+/.py) pre-inserted as target and search 
directory, and options as radiobuttons (remembered from my last search) ...

> You will get a list of hits in a new buffer. You can use the C-x `
> command to traverse them in order, but there are many other ways.

and a scrollable window for results ;-).

-- 
Terry Jan Reedy

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

#72349

On Fri, 30 May 2014 13:53:06 +0100, Rustom Mody <rustompmody@gmail.com>  
wrote:

> On Thursday, May 29, 2014 10:14:35 PM UTC+5:30, Paul Rudin wrote:
>> Terry Reedy writes:
>> > 3. Search unopened files (grep) for a string or re.
>
>> Emacs.
>
> How do you do this with emacs?
> I find a menagerie of greppish commands -- rgrep, lgrep, grep-find etc

I generally find "M-x grep" sufficient.

-- 
Rhodri James *-* Wildebeest Herder to the Masses

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

#72244

On Fri, May 30, 2014 at 2:39 AM, Terry Reedy <tjreedy@udel.edu> wrote:
> I am curious how many of the editors people have been recommending have all
> of the following Idle features, that I use constantly.

Regarding SciTE:

> 1. Run code in the editor with a single keypress.

Yes, although for most of what I like to do, it's not appropriate. But
if you're developing a script that runs and then terminates, yes, you
certainly can.

> 2. Display output and traceback in a window that lets you jump from the any
> line in the traceback to the corresponding file and line, opening the file
> if necessary.

Yes; it recognizes the most common formats used by C compilers, as
well as Python's traceback. Pressing F4 repeatedly will cycle you
through the output pane, effectively taking you from one step to
another in the traceback. (Obviously if you have more than one
traceback, it'll go straight from one to another, which won't always
be useful.) You can also double-click a line to go straight there.

> 3. Search unopened files (grep) for a string or re.

Yes, either using grep itself (fourth point) or using an internal
search that's more akin to an old DOS or OS/2 style of search. Either
way, the results come up in the output pane, and F4 will cycle through
them.

> 4. Display grep output in a window that lets you jump from any 'hit' to
> the corresponding file and line, opening the file if necessary.

As above. These three are all one feature, really. You can type
commands in the output pane and they'll be executed; any program
output that matches one of its parseable "this file, this line"
formats (which is true of 'grep -n') will be picked up.

ChrisA

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

#72253

On 5/29/2014 12:51 PM, Chris Angelico wrote:
> On Fri, May 30, 2014 at 2:39 AM, Terry Reedy <tjreedy@udel.edu> wrote:
>> I am curious how many of the editors people have been recommending have all
>> of the following Idle features, that I use constantly.
>
> Regarding SciTE:
>
>> 1. Run code in the editor with a single keypress.
>
> Yes, although for most of what I like to do, it's not appropriate. But
> if you're developing a script that runs and then terminates, yes, you
> certainly can.
>
>> 2. Display output and traceback in a window that lets you jump from the any
>> line in the traceback to the corresponding file and line, opening the file
>> if necessary.
>
> Yes; it recognizes the most common formats used by C compilers, as
> well as Python's traceback. Pressing F4 repeatedly will cycle you
> through the output pane, effectively taking you from one step to
> another in the traceback. (Obviously if you have more than one
> traceback, it'll go straight from one to another, which won't always
> be useful.) You can also double-click a line to go straight there.
>
>> 3. Search unopened files (grep) for a string or re.
>
> Yes, either using grep itself (fourth point) or using an internal
> search that's more akin to an old DOS or OS/2 style of search. Either
> way, the results come up in the output pane, and F4 will cycle through
> them.
>
>> 4. Display grep output in a window that lets you jump from any 'hit' to
>> the corresponding file and line, opening the file if necessary.
>
> As above. These three are all one feature, really.

Thank you. This makes your recommendation understandable.

 > You can type
> commands in the output pane and they'll be executed; any program
> output that matches one of its parseable "this file, this line"
> formats (which is true of 'grep -n') will be picked up.

Find in Files (grep) is implemented within Idle, in Python, using re. 
One of the subprojects of this summer's Idle GSOC student, Saimadhav 
Heblikar, is to add to Idle something similar to what you describe 
above. Run an external code analyzer (PyLint/Flake/Checker, 
whatever...), capture output, and jump to indicated locations. For Idle, 
the prime intended use would, of course, be for analyzing Python files.

-- 
Terry Jan Reedy

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

#72254

Terry Reedy <tjreedy@udel.edu> writes:

> I am curious how many of the editors people have been recommending
> have all of the following Idle features, that I use constantly.

You can satisfy such wonderings with a search for the answers to such
questions, which is how I got these answers.

> 1. Run [Python] code in the editor with a single keypress.

That's not very clear. If you mean, run the entire file being edited:
yes, Vim and Emacs can do that.

I don't use such a feature, because I almost never want to run the
*entire* module; I want to test the one function I'm working on at that
moment. For that purpose, a unit test is more appropriate.

Vim and Emacs also have the feature to run a Python unit test suite with
a single key and navigate the output.

> 2. Display output and traceback in a window that lets you jump from
> the any line in the traceback to the corresponding file and line,
> opening the file if necessary.

Yes, any decent programmer's editor will have this, once it is taught
how to parse the error output from the language interpreter.

For Vim and Emacs, yes, they already know how to capture error output
and interactively jump to the referenced locations in the code.

They also both have interactive debugger modes, including for Python.

> 3. Search unopened files (grep) for a string or re.
> 4. Display grep output in a window that lets you jump from any 'hit'
> to the corresponding file and line, opening the file if necessary.

This is an essential feature of any decent programming editor, and Vim
and Emacs certainly have the feature to grep a file tree and navigate
the results interactively.

-- 
 \      “[Entrenched media corporations will] maintain the status quo, |
  `\       or die trying. Either is better than actually WORKING for a |
_o__)                  living.” —ringsnake.livejournal.com, 2007-11-12 |
Ben Finney

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

#72258

> On May 28, 2014, at 3:43, Sameer Rathoud <sameer.rathoud@gmail.com> wrote:
> 
> Hello everyone,
> 
> I am new to python.
> 
> I am currently using python 3.3
> 
> With python I got IDLE, but I am not very comfortable with this.
> 
> Please suggest, if we have any free ide for python development.
> -- 
> https://mail.python.org/mailman/listinfo/python-list

I use either vim or textwrangler for simple one file scripts. For larger things with multiple files and/or classes, I like pycharm best ( free community edition ). I tried both pydev and wing before that.

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

#72285

On 2014-05-29 22:40:36 +0000, Travis Griggs said:

> I use either vim or textwrangler for simple one file scripts.

Since you're on OS X have a look at Exedore, it's paid but very cheap. 
It aims at providing a beautiful interface, I fetched the free trial a 
couple days ago and the job so far is impressively neat.

I'm not related to the project, I just found it by accident and want to 
give Cocoa-credit where credit is due.


-- 
Andrea

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

#72291

On 2014-05-30 07:21:52 +0000, Andrea D'Amore said:
> It aims at providing a beautiful interface,

Side note: the text editing is still green.


-- 
Andrea

[toc] | [prev] | [standalone]

Page 4 of 4 — ← Prev page 1 2 3 [4]

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

csiph-web