ript with a different
Python (e.g. /usr/bin/python3s vs. /usr/bin/python3) to get the full unpacked
source, that would be fine.
Cheers,
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
he binary. I've applied and submitted several
patches to various upstreams that help with this effort, such as being able to
pass in "locked" datetimes instead of the package always using
e.g. datetime.now().
Let's not dive down the rabbit hole too far into how you can trust your
Right or wrong, could you please add a paragraph explaining the meaning of the
underscores?
Cheers,
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org
On Feb 11, 2016, at 05:57 PM, Georg Brandl wrote:
>D'oh :) I added (hopefully) clarifying wording.
I saw the diff - perfect! Thanks.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/py
As BDFL-Delegate, I am officially accepting PEP 493.
Congratulations Nick, Robert, and MAL. I want to personally thank Nick for
taking my concerns into consideration, and re-working the PEP to resolve
them. Thanks also to everyone who contributed to the discussion.
Cheers,
-Barry
m to work better with other libraries (both stdlib and 3rd party) that
will continue to be os.path based for the foreseeable future.
Cheers,
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/pyt
't have to be 100% but this would be a big improvement.
Cheers,
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
t encode
to utf-8 and had a UI to allow the user to fix the name.
One reason for files that can only be represented as bytes()
being detectable I suspect is to avoid security issues. I think
if I have my black hat on I would probe a python3 app with filenames
that are non-utf-8 and s
On Apr 14, 2016, at 09:49 PM, Victor Stinner wrote:
>It would be nice to hear Barry Warsow who was opposed to the PEP in
>january. He wanted to wait until FAT Python was proven to really be faster,
>which is still not case right now. (I mean that I didnt't run seriously
>benc
> From Armin Rigo
> Sent: Thursday, April 14, 2016 4:42 PM
> To: Victor Stinner
> Cc: Python Dev
> Subject: Re: [Python-Dev] RFC: PEP 509: Add a private version to dict
>
> Hi Victor,
>
> On 14 April 2016 at 17:19, Victor Stinner wrote:
> > Each time a dictionary is created, the global
> > versi
lock around incrementing the global version number.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
On Apr 15, 2016, at 09:53 AM, Guido van Rossum wrote:
>After a fruitful discussion on python-ideas I've decided that it's fine to
>break lines *before* a binary operator.
Thanks Guido, your changes look great.
-Barry
___
Python-Dev mai
On Apr 21, 2016, at 10:43 PM, Chris Angelico wrote:
>I still have no clue what you're talking about. Every project has a
>leader. If Guido dies, goes insane [1], or gets bored with the Python
>project, someone else can and will take over.
Fortunately, the Python Secret Underground (PSU) which mos
turns on full personalization so the footers will all have a link to
your unsubscribe page. As Ben pointed out, we also implement RFC 2369, which
is only an 18 year old standard.
Cheers,
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://m
ver think to
>look) is a requirement for the CanSpam act, or whatever it was called.
BTW, the whole point of RFC 2369 headers is so that MUAs can implement a nice
big fat blinky UNSUBSCRIBE button in their UI.
-Barry
___
Python-Dev mailing list
there's the friendly fork:
https://pypi.python.org/pypi/Pillow/3.2.0
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
ted: 11-May-2016
>Post-History: 11-May-2016,
> 12-May-2016,
> 13-May-2016
I think this is far enough along that you should self-assign a PEP number and
check it into the official repo.
Cheers,
-Barry
___
Python-Dev m
.1...
Please, no. We learned that lesson in Python 2.2.1 with True/False.
Cheers,
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-d
> From: Python-Dev [mailto:python-dev-
> bounces+vgr255=live...@python.org] On Behalf Of tritium-
> l...@sdamon.com
> Sent: Sunday, June 05, 2016 10:35 PM
> To: 'Sturla Molden'; python-dev@python.org
> Subject: Re: [Python-Dev] C99
>
> > -Original Message-
> > From: Python-Dev [mailto:pyth
On Jun 06, 2016, at 01:02 PM, Łukasz Langa wrote:
>There’s a problem with this approach. It will force people to write
>deprecated code because you never know if your library is going to run on
>3.5.0 or 3.5.1. Barry, Ubuntu wily, xenial and yakkety currently package
>3.5.0 or 3.5.1
> From: Ethan Furman
> Sent: Tuesday, June 07, 2016 1:38 PM
> To: Python Dev
> Subject: [Python-Dev] Proper way to specify that a method is not defined
for
> a type
(Just so everyone follows, this is a followup of
http://bugs.python.org/issue27242 )
> For binary methods, such as __add__, either d
).
Ha! The only thing I don't much like about ExitStack is its capword name. ;)
I don't have a problem breaking PEP 8 rules for cases like this.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/list
).
I think PEP 8 needs to be slightly revised. If you have suggestions for better
wording, please comment here:
http://bugs.python.org/issue19331
(But *please* let's not bikeshed this on python-dev.)
-Barry
___
Python-Dev mailing list
Pytho
that should go into Python 2.6 but has not yet, please
contact me asap. Please test rc1 on your platforms and code, and let me know
if you have any problems.
Barring any showstoppers, I will likely cut the release AM my local time.
Cheers,
-Barry
signature.asc
Description: PGP signature
just a quick verification that your download succeeded. For extra
confidence, check the signatures. Our keys should be independently
verifiable.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/pyth
final is scheduled for Monday, so if
there's something we need to get in before then, please let me know asap.
Cheers,
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https:/
es, but I think that's acceptable
given how old 2.6 is (EOL) and how new 10.9 is.
If 10.9 had come out two weeks from now, "do nothing" would have been the
obvious answer. :) So unless I hear strong objections before next Monday, I am
not going to fix this in 2.6.9.
Cheers,
-Barr
se page. That way
we can still use the tracker to manage patches for 2.6, even though they won't
be officially applied.
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mail
9/NEWS.txt
Users on OS X 10.9 (Mavericks) please note that issue 18458, which can crash
the interactive interpreter, is *not* fixed in 2.6.9. If this issue affects
you, please review the tracker for possible options:
http://bugs.python.org/issue18458
Enjoy,
-Barry
(on behalf of the Pyt
om
firing up the other. So yes, I think Vim would have to put that guard in, and
I agree that there's not much benefit in trying to make this work in Python.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman
the SSLContext object, such that clients of the client code can load up those
self-signed certificates after the context has been created.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
51/
Congratulations for all the hard work on a great PEP.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
xgettext can't handle
that pygettext can, we should help to fix the former.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/
lem that I had while addressing these options in
Debian was the use of .pyo for both -O and -OO level.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mai
n
if/elif on an enumeration where the else should never be hit. Or saying that
after some calculation, this variable can never be None. In a sense,
assertions are executable documentation about the state of behavior at a
particular line of code. If an assert ever *does* get triggered, it means
of course.
I think you're just going to confuse everyone if you call it "Stackless Python
2.8" and it will do more harm than good.
Cheers,
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo
ggesting this particular case ever
escalate to such a level. Chris is our friend and a nice guy. :)
I'm just saying that I think we should avoid any possible confusion on the
part of ours (and Stackless's) users. And based on the discussions here,
there are
nts, but I would strongly oppose the
use of the word "Python" in that. I don't want to be antagonistic, but I
think the PSF should also oppose allowing the use of the trademark for
any association with an unofficial 2.8.
-Barry
___
t this is not acceptance of PEP 436, which has still not gotten formal
approval afaict. We'll need that in order to change the status on the PEP,
with a Resolution header. Larry, is the PEP ready to be pronounced upon?
-Barry
___
Python-Dev
On Nov 22, 2013, at 03:55 PM, Antoine Pitrou wrote:
>(perhaps Barry will play a bass solo? :-))
Now, now, we don't want to give Chris incentive, do we? :)
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org
ox. It's
unsupported hardware and barely limping along.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
It would be fine(-ish) to add this for improved buildbot performance, but
please do not change this for default --with-pydebug builds. When you're
debugging Python, -O0 just makes so much more sense.
-Barry
___
Python-Dev mailing list
Python-Dev
stuck at Ubuntu 12.10.)
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
On Nov 24, 2013, at 06:02 PM, Antoine Pitrou wrote:
>If the hardware is not supported anymore, and since the machine was
>rather slow, I agree it's ok to let it go.
Done!
(The machine's name was 'hope', so now we're hope-less :).
-Barry
___
On Dec 09, 2013, at 04:00 PM, TaeWong wrote:
>The name Jonas Wagner comes before Zachary Ware and Barry Warsaw.
Maybe it's time to give up on trying to sort by last name, and just sort by
first character?
No, this is not a bold attempt to jump higher up in the list.
-AAA
ackery to figure out whether
the old API was being used (keys: int, default, maxwidth) or the new API was
being used (keys: _int and _maxwidth). Yeah it's ugly, but we serve our users
better by doing it that way.
Cheers,
- -Barry
-BEGIN PGP SIGNA
ngle place in the C module file, for
> example near the end (Larry's "accumulator" idea)
+1
>- prefix all Clinic-generated lines with a recognizable marker, e.g.
> "/* AC */"
+0
-Barry
___
Python-Dev mailing list
{dict[key]}
* format keywords? b'{arg}'.format(arg=5)
* str % dict ? b'%(arg)s' % {'arg': 5)
These are just lookup mechanisms for finding the wanted interpolation value
and don't have encoding or conversion effects.
Cheers,
-Barry
___
in Ubuntu), but if
PEP 460 helps speed up the transition of the rest of the suite, I'm all for
trying to squeeze it into 3.4.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
disagree. The Python interpreter is
the lowest rung of the food chain, so there's a natural delay in having
required support percolate up. Imposing another 18 month delay would be
unfortunate. (Obviously, if technical matters prevent it, that's another
thing.)
-Barry
signature.a
On Jan 07, 2014, at 11:13 PM, Antoine Pitrou wrote:
>On Tue, 7 Jan 2014 15:46:50 -0500
>Barry Warsaw wrote:
>>
>> If adopted for Python 3.4, PEP 460 should be modest in its goals, but I think
>> I'd still like to see the following excluded and unknown features adde
ual code, and I suspect even Guido could be influenced if he could pull
some things up in his editor and take a look around.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
ht
rting the library, and for the more general insights
it could provide for this thread, please get in touch.
Cheers,
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/li
(really, it's wonderful :).
I plan on keeping more detailed notes this time specifically so that I can
help contribute to this discussion. If anybody wants to pitch in, both for
the specific purpose of porting the library, and for the more general insights
it could provide
inal decision. Then the PEP can be amended with those decisions, and if
folks still think more needs to be done, a follow up PEP can be filed.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Un
nately causes no end of headaches, often difficult to debug.
https://wiki.python.org/moin/PortingToPy3k/BilingualQuickRef
(see 'doctests' for one such impact).
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mail
the user visible error is far removed from the actual bug, both in
code distance and time. So yes, it tells you Something Went Wrong, but is
actually a hindrance to finding and fixing the problem.
-Barry
___
Python-Dev mailing list
Python-Dev@python.o
The behavior of b'%s' % 'x' returning b"'x'" is almost
always useless at best. (I would have thought maybe %a for ascii() but don't
care that strongly.)
-Barry
signature.asc
Description: PGP signature
sed (e.g. you are
parsing messages being fed to you from your mail server).
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
On Jan 17, 2014, at 11:00 AM, Brett Cannon wrote:
>I would rephrase it to "switch to %-formatting for bytes usage for their
>common code base".
-1. %-formatting is so neanderthal. :)
-Barry
___
Python-Dev mailing list
Python-Dev@
his seems like a nice parallel to __pycache__. It's mostly hidden until
you want to go looking for it.
+1
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.
t;use it not only to generate pyc files.
marshall is not guaranteed to be backward compatible between Python versions,
so it's generally not a good idea to use it for serialization.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https:
>will blow up. But if they don't use PyMethodDefEx, they can't have
>signatures.
Can't an extension writer #ifdef around this? Yeah, it's ugly, but it's a
pretty standard approach for making C extensions multi-version compatible.
-Barry
__
3.5.
At the very least, it's an idea worth PEP-ifying.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
r !larry sure, but not private.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
le to get to everything in universe).
Matthias just switched the default for Ubuntu 14.04 to Python 3.4 by default,
so this is a great test bed to find problems.
Cheers,
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python
release schedules
with external schedules before, most notably Apple a couple of times. I think
it's reasonable to do so *if* we can do it without sacrificing the quality of
Python 3.4's final release.
Cheers,
-Barry
[1] https://wiki.ubuntu.com/TrustyTahr/ReleaseSchedule
___
picked. Let's not hobble this API for all
eternity if it can be fixed before the release.
Thanks for working so hard to make enums great in Python 3.4.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/
tion in Python 2.7, because of questions like these. The same
analysis would have to be done for backporting this change to active older
Python versions.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/pyth
s at best
confusing. Despite my hesitation to paint a bike shed I haven't had time to
inspect, something more akin to Py_SET_POINTER seems more appropriate
(i.e. don't put "REF" in the name if it isn't playing refcounting games).
-Barry
TEM macros do.
>
>That actually gives me an idea that wasn't on Serhiy's original list:
>Py_SET_ATTR(target, value).
That does seem better.
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@
On Mar 03, 2014, at 10:36 PM, Mark Lawrence wrote:
>Will this impact on the decision http://bugs.python.org/issue20846 ?
Issue 20808 is my own pet cherry pick for 3.4.
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing l
p improve the stability of the
>final release, and wherever practical, we should be doing our best to
>encourage it.
Given how difficult it is to get people to test pre-final release versions, I
definitely agree we need to encourage and support enthus
e module doesn't actually come from a "file", there's no longer a
requirement to craft some mythical value for it if it doesn't make sense.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listin
e have at least
9 years before we have to worry about that. ((~3.10 - 3.4) * 18months)).
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/p
On Mar 10, 2014, at 04:25 PM, Stefan Richthofer wrote:
>> I don't see any reason to bump
>> the major version number until after Python 3.9.
>
>Even then, there is no need for 4.0; you can just have 3.10, 3.11 etc.
Guido famously hates two digit minor vers
On Mar 12, 2014, at 11:14 AM, Brett Cannon wrote:
>While I'm +0 on the idea, I'm -1 on the syntax; I just don't like having a
>colon in an expression.
I'm -0 on the idea, mostly be cause it's never occurred to me to even need
something like this, and because I don't personally think the existing
ng the python-dev/python-ideas gauntlet! That's an accomplishment
even if the PEP is rejected.
Cheers,
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
hard for you to accept
>the fact that your "inline try/except" idea is maybe not as good as
>you expected :-)
Don't worry, there's always Python 4 .
http://legacy.python.org/dev/peps/pep-0274/
-Barry
___
Python-Dev mailing li
On Mar 14, 2014, at 04:48 PM, Nick Coghlan wrote:
>I opened https://github.com/python/pythondotorg/issues/297 to ask for
>an ETA on when we can expect them to be fully integrated.
Thanks Nick. On the bug I suggest creating peps.python.org.
-Barry
signature.asc
Description: PGP sig
On Mar 18, 2014, at 08:29 PM, Serhiy Storchaka wrote:
>Poll results:
>
>Py_(X)SETREF: +3 (Antoine, Kristján, Nick)
+1
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscrib
k-wink-nudge-nudge release of
Python 2.8.
I think the key point for consumers of Python has to be *predictability*.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
p it distinct and independent of the system's standard Python
2.7?
Maybe this is some scent of Python 2.8 by another name, but let's never call
it Python 2.8.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/m
uirements and I think it will be difficult
to satisfy everyone. I'm particularly sensitive to complaints of unexpected
changes between micro releases.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinf
pful in resolving the
>situation amicably for the benefit of all concerned, so I'll revise
>the offending sections of the PEP :)
Anger management through PEP writing! That's novel, but I can show you some
more effective techniques at Pycon. :)
-Barry
_
ves most of the concerns I had about it. It maintains the backward
compatibility pledge but relaxes the new feature backport prohibition where
security concerns trump.
Cheers,
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.o
ble that you won't mind the Python
stdlib 18 month development cycle, then you can propose that it be included in
Python.
Cheers,
-Barry
[1] http://docs.python.org/devguide/experts.html
___
Python-Dev mailing list
Python-Dev@python.org
https
ot.
Hmm, me neither! I guess if someone *wants* to go through the PEP gauntlet, I
won't stop them. It builds character.
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.pyt
ile "", line 1
'flufl' != 'bdfl'
^
SyntaxError: invalid syntax
(And no, I am not recommending you actually *use* that in live code. :)
flufl-ly y'rs,
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
On Apr 07, 2014, at 06:06 PM, Benjamin Peterson wrote:
>> > It occurs to me that since that Aprils' Fools joke is many years old
>> > now, we should remove it.
>>
>> -1 on removal.
>
>You can't be serious
On Apr 07, 2014, at 06:13 PM, Benjamin Peterson wrote:
>On Mon, Apr 7, 2014, at 18:11, Barry Warsaw wrote:
>> On Apr 07, 2014, at 06:06 PM, Benjamin Peterson wrote:
>>
>> >> > It occurs to me that since that Aprils' Fools joke is many years old
>> >&
al implementation details -- makes a PEP even more important here.
Agreed. We've already started down the slippery slope of bundling third party
packages (e.g. the ensurepip dependencies) and this is causing headaches for
some of us distro guys. Either they're in the s
hon 2 and 3 from a single source
"bi-lingual". Maybe we've just been mispronouncing "py-lingual" :).
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscrib
d this is even
>more true for projects massively centered around IO, such as Twisted and,
>I'm sure, the main (only?) reason why Twisted hasn't been ported yet.
I agree. I've been trying to get rid of iter*() when porting because most of
the time, there is no signifi
ect comes up with its own guidelines and applies them
self-consistently. For example, I have my own small set of refinements on top
of PEP 8. I'm not providing a link because they're a bit out of date
w.r.t. Python 3. ;)
Cheers,
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
t's Go's flavor of Python's whitespace rule. :)
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
m line length) for new projects;
I'd say it depends. If the code is going to be shared with people outside of
your organization (e.g. open source libraries), then there's a strong
motivation to be consistent throughout the community, which means PEP 8.
-Barry
__
line of that style guide should be:
`PEP 8`_ is the basis for this style guide so its recommendations
should be followed except for the differences outlined here.
:)
cheers,
-Barry
signature.asc
Description: PGP signature
___
Python-De
d in this situation maybe verbiage to that effect could be added.
No, I think it's a typo and should be 4 spaces. I'll fix that.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsub
that your arguments are indented too far to the right. But e.g. this would be
fine:
foo = long_function_name(var_one,
var_two=a_value,
var_three=some_other_value,
var_four=(a, tuple, of, values)
)
Cheers,
-Barry
signa
301 - 400 of 2826 matches
Mail list logo
