From: Joseph Myers <joseph@codesourcery.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: <libc-alpha@sourceware.org>
Subject: Re: Add script to build many glibc configurations
Date: Mon, 14 Nov 2016 23:28:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1611142325500.32454@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20161114192719.GW21655@vapier.lan>
On Mon, 14 Nov 2016, Mike Frysinger wrote:
> On 14 Nov 2016 15:22, Joseph Myers wrote:
> > On Mon, 14 Nov 2016, Mike Frysinger wrote:
> > > > +class Context:
> > >
> > > please no old style classes. all of them should inherit object.
> > > class Context(object):
> >
> > There's no such thing as an old-style class in Python 3 (and this script
> > requires 3.5 or later); inheritance from object happens by default.
>
> the py3 behavior is irrelevant to the style choice: the object inherit
> should be explicit regardless.
Is there some style guide we're following that recommends this for Python
3 code? I've only seen it mentioned as something to do when you're
writing code that's meant to work the same in Python 2 and Python 3, not
for code unconcerned with Python 2 compatibility.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2016-11-14 23:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 16:27 Joseph Myers
2016-11-10 14:27 ` Joseph Myers
2016-11-10 16:44 ` Joseph Myers
2016-11-23 17:36 ` Chris Metcalf
2016-11-10 17:09 ` Steve Ellcey
2016-11-10 17:22 ` Joseph Myers
2016-11-10 17:39 ` Steve Ellcey
2016-11-11 15:20 ` Joseph Myers
2016-11-11 19:37 ` Carlos O'Donell
2016-11-14 15:06 ` Mike Frysinger
2016-11-14 15:23 ` Joseph Myers
2016-11-14 19:27 ` Mike Frysinger
2016-11-14 23:28 ` Joseph Myers [this message]
2016-11-14 23:57 ` Joseph Myers
2016-11-17 16:52 ` Zack Weinberg
2016-11-17 17:26 ` Zack Weinberg
2016-11-17 17:47 ` Joseph Myers
2016-11-17 17:54 ` Andreas Schwab
2016-11-17 17:51 ` Joseph Myers
2016-11-18 16:28 ` Zack Weinberg
2016-11-18 18:27 ` Joseph Myers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1611142325500.32454@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=vapier@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).