Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.albasani.net!weretis.net!feeder4.news.weretis.net!ecngs!feeder2.ecngs.de!novso.com!newsfeed.xs4all.nl!newsfeed4a.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
In-Reply-To: <17ed0132-89d5-4b45-81b5-b61328a21198@googlegroups.com>
References: <9fc57fc9-0399-4ff3-882a-d041f02827d8@googlegroups.com> <6580b5d5-92f5-4bfa-b1d0-889c69fe82bb@googlegroups.com> <mailman.374.1429285961.12925.python-list@python.org> <mgrcb5$sn2$1@reader1.panix.com> <Y3bYw.302660$ms.24839@fx30.am4> <mailman.388.1429323788.12925.python-list@python.org> <7tMYw.252071$SO1.39320@fx43.am4> <mailman.405.1429456511.12925.python-list@python.org> <7413a8e7-b580-4b2f-84bc-dd13da2d36ba@googlegroups.com> <5533eb85$0$12992$c3e8da3$5496439d@news.astraweb.com> <16d59891-6e28-4256-870a-903bb75aa953@googlegroups.com> <mailman.3.1429496666.31470.python-list@python.org> <a745d401-190d-4e7b-bc90-85f7e2cd6504@googlegroups.com> <mailman.5.1429499040.31470.python-list@python.org> <17ed0132-89d5-4b45-81b5-b61328a21198@googlegroups.com>
Date: Mon, 20 Apr 2015 13:44:08 +1000
Subject: Re: New to Python - block grouping (spaces)
From: Chris Angelico <rosuav@gmail.com>
Cc: "python-list@python.org" <python-list@python.org>
Content-Type: text/plain; charset=UTF-8
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.7.1429501451.31470.python-list@python.org>
Lines: 45
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:89197

On Mon, Apr 20, 2015 at 1:28 PM, Rustom Mody <rustompmody@gmail.com> wrote:
>> If you have a ten-file project that's identifying a key function
>> globally as 'f', then you already have a problem. If your names are
>> more useful and informative, a global search-and-replace will do the
>> job.
>
> Are you sure your global search-and-replace will do a proper job inside
> strings and comments?

Yep! Any occurrence inside a string literal or comment is generally
going to be referring to the same function, and thus should be
renamed. Can your system handle _that_? Example:

def add_grab(widget):
    """Add a widget to the grabbed widgets"""

def remove_grab(widget):
    """Undo the effect of add_grab() on a given widget"""
    # Note that multiple add_grab() calls will add multiple instances,
    # so we remove only the first.

Every occurrence of add_grab here is referring to the function. If you
do a global search-and-replace, they'll be caught automatically. With
your non-text magic, you'd need to explicitly implement this as a
feature. Text files make life easier!

>> What's your point, though?
>
> Point?
>
> Nnotions like identifier (and dozens of others) are straightforwardly
> present and available inside the python implementation.
> However the language implementation is a hard-n-high silo
> For the programmer accessing the language through an editor these notions are
> not available unless hi-power explosives are used to punch holes in the silo
> -- eg open Cpython sources.

Would it help if Python grew a function like Pike's
Function.defined(), which tells you exactly where, even in C source,
something was defined? I don't honestly see that looking in the
CPython source is such a common need that it begs for assistance, and
I definitely don't see how a non-text source code format would improve
on it. Feel like elaborating?

ChrisA