Hi,
I don't think a leading _ is the way to go, because that's a common
convention for internal class variables--property variables that you don't
intend to be part of any supported API.
Personally, I've always just called things like this "junk" or "unused",
but I know that's not as nice as having a symbolic notation.
Ryan
On Thu, Mar 6, 2014 at 11:38 AM, Skip Montanaro <s...@pobox.com> wrote:
> On Thu, Mar 6, 2014 at 7:47 AM, Federico Ariza <ariza.feder...@gmail.com>
> wrote:
> > Stupid simple question
> > Is there a policy/tradition/convention to name unused variables inside
> the code?
>
> While Eric indicates there is no policy, for the Python parts of your
> code, I recommend you follow whatever the default is that pylint or
> one of the other lint-like checkers recommend. Pylint likes a leading
> underscore, but if you have a different natural preference, I
> recommend you post your query at code-qual...@python.org. It's where
> all the cool static checker folk hang out. I haven't read PEP 8 in a
> long while. Does Guido express a preference there?
>
> Skip (not a cool static checker guy)
>
>
> ------------------------------------------------------------------------------
> Subversion Kills Productivity. Get off Subversion & Make the Move to
> Perforce.
> With Perforce, you get hassle-free workflows. Merge that actually works.
> Faster operations. Version large binaries. Built-in WAN optimization and
> the
> freedom to use Git, Perforce or both. Make the move to Perforce.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
--
Ryan May
Graduate Research Assistant
School of Meteorology
University of Oklahoma
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
