I'm real naive about this stuff, but I have always wondered why
matplotlib didn't just use datetime objects, or at least use
timezone-aware datetime objects as an "interchange" format to get the
timezone stuff right.
Skip
---
The nascent 1.4.x code is working fine for me to fire up my
interactive graphs served by a Tornado server. I'm interested in
providing an interface via a web application server like Django
though. I've only begun to look at the webagg backend code, but if I
read the comments correctly at the top of
On Mon, May 12, 2014 at 10:31 AM, Benjamin Root wrote:
> No, it gets used. We just have a huge backlog of issue tickets to go
> through.
>
> At first glance, I think this problem has already been reported and fixed in
> master. Can you try building from source the master branch on github and
> see
On Wed, May 7, 2014 at 9:04 AM, Skip Montanaro wrote:
> I'm trying to use the webagg backend for the first time, and seem to
> be bumping into a common problem - nothing appears.
I'm guessing that the complete lack of response both here and on
matplotlib-users means nobody
Apologies for those of you seeing this for a second time. I've
received no response on matplotlib-users, so I'm turning to the
experts.
In one message, I wrote:
I'm trying to use the webagg backend for the first time, and seem to
be bumping into a common problem - nothing appears. The fir
On Thu, Mar 6, 2014 at 3:58 PM, Chris Barker wrote:
> it looks like pylint, anyway, will accept that.
Yes, pylint used to only accept a leading underscore by default as a
flag that a variable was unused. When I switched from pychecker to
pylint a few years ago, all my carefully crafted "unused_"
On Thu, Mar 6, 2014 at 3:13 PM, Nelle Varoquaux
wrote:
> If I need to understand what exactly os.stat returns, I just read the
> documentation, and not rely on some possibly misleading variable
> names.
Despite our wish that it wasn't so, it is likely that there is far
more undocumented than docu
On Thu, Mar 6, 2014 at 2:51 PM, Nelle Varoquaux
wrote:
> The convention is to use a simple _.
>
> mode, _, dev, nlink, uid, gid, size, _, _, _ = os.stat("/etc/hosts")
Which is "pylint-compliant", but removes any description to future
readers (who might decide to use them) what the meaning of tho
On Thu, Mar 6, 2014 at 2:38 PM, Ryan May wrote:
> 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.
But leading underscores like this are only used as attribute
On Thu, Mar 6, 2014 at 7:47 AM, Federico Ariza 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 pyli
10 matches
Mail list logo
