Re: [Python-Dev] pep8 reasoning

2014-04-24 Thread Steven D'Aprano
On Thu, Apr 24, 2014 at 01:57:38PM +0100, Tim Golden wrote: > On 24/04/2014 12:59, Tal Einat wrote: > > As far as I know that reason for these examples being frowned upon is > > that they are needlessly redundant. > > Oh, the irony! (Sorry, couldn't resist) Not really ironic, since not all redun

Re: [Python-Dev] pep8 reasoning

2014-04-24 Thread Guido van Rossum
On Apr 24, 2014 7:01 PM, "Chris Angelico" wrote: > > On Fri, Apr 25, 2014 at 11:40 AM, Allen Li wrote: > > 2) If you're starting a new project, follow PEP8 (or the standards for > >the language you're using) to preserve CONSISTENCY. > > Don't forget that PEP 8 is not the standard for the Pyth

Re: [Python-Dev] pep8 reasoning

2014-04-24 Thread Greg Ewing
Chris Angelico wrote: add_HTTP_header add_http_header addHTTPHeader addHttpHeader Five... there are FIVE options... convertXMLtoJSON i.e. don't capitalise a part that follows capitalised initials. -- Greg ___ Python-Dev mailing list Python-Dev@py

Re: [Python-Dev] pep8 reasoning

2014-04-24 Thread Barry Warsaw
On Apr 25, 2014, at 12:00 PM, Chris Angelico wrote: >Don't forget that PEP 8 is not the standard for the Python language, >only the Python stdlib. Particularly, there's no strong reason to >follow some of its lesser advices (eg spaces rather than tabs, the >exact maximum line length) for new proje

Re: [Python-Dev] pep8 reasoning

2014-04-24 Thread Chris Angelico
On Fri, Apr 25, 2014 at 11:40 AM, Allen Li wrote: > 2) If you're starting a new project, follow PEP8 (or the standards for >the language you're using) to preserve CONSISTENCY. Don't forget that PEP 8 is not the standard for the Python language, only the Python stdlib. Particularly, there's no

Re: [Python-Dev] pep8 reasoning

2014-04-24 Thread Allen Li
On Thu, Apr 24, 2014 at 11:36:03AM -0500, Tim Peters wrote: > There's been a bit of serious study on this. The results are still > open to interpretation, though ;-) Here's a nice summary: > > http://whathecode.wordpress.com/2011/02/10/camelcase-vs-underscores-scientific-showdown/ To summarize

Re: [Python-Dev] pep8 reasoning

2014-04-24 Thread Glenn Linderman
On 4/24/2014 11:01 AM, Daniel Holth wrote: Fortunately, Unicode provides us with the COMBINING LOW LINE character, combining the horizontal space-savings of camelCase with the underscore-indicates-separation properties of _. And it's a valid Python identifier. convertx̲mlt̲oj̲son That should b

Re: [Python-Dev] pep8 reasoning

2014-04-24 Thread Tim Peters
[Tim] >> There's been a bit of serious study on this. The results are still >> open to interpretation, though ;-) Here's a nice summary: >> >> >> http://whathecode.wordpress.com/2011/02/10/camelcase-vs-underscores-scientific-showdown/ [Terry Reedy] > The linked poll is almost evenly split, 52% t

Re: [Python-Dev] pep8 reasoning

2014-04-24 Thread Terry Reedy
On 4/24/2014 12:36 PM, Tim Peters wrote: There's been a bit of serious study on this. The results are still open to interpretation, though ;-) Here's a nice summary: http://whathecode.wordpress.com/2011/02/10/camelcase-vs-underscores-scientific-showdown/ The linked poll is almost evenly spli

Re: [Python-Dev] ref leaks

2014-04-24 Thread R. David Murray
On Thu, 24 Apr 2014 17:17:41 +0200, Stefan Krah wrote: > Ethan Furman wrote: > > >>Any words of wisdom for tracking those leaks? > > Often the easiest way is to compile --with-valgrind and run the test > under Valgrind (obviously). > > In the Valgrind output, search for "definitely lost" and ig

Re: [Python-Dev] static typing of input arguments in signatures

2014-04-24 Thread Łukasz Langa
On Apr 19, 2014, at 11:05 AM, Ethan Furman wrote: > Personal experience: I have my own copy of paramiko because it type checks > for strings, and I routinely use a str-subclass. I have had that kind of problem myself in the past. Most of the time the core issue wasn’t type checking, it was ho

Re: [Python-Dev] pep8 reasoning

2014-04-24 Thread Daniel Holth
Fortunately, Unicode provides us with the COMBINING LOW LINE character, combining the horizontal space-savings of camelCase with the underscore-indicates-separation properties of _. And it's a valid Python identifier. convertx̲mlt̲oj̲son On Thu, Apr 24, 2014 at 12:25 PM, Chris Angelico wrote:

Re: [Python-Dev] pep8 reasoning

2014-04-24 Thread Barry Warsaw
On Apr 24, 2014, at 06:51 PM, Tal Einat wrote: >I speak two languages as mother tongues - English and Hebrew. Hebrew >has no capital letters (and is also right-to-left) and is the spoken >and written language in the parts of Israel where I've lived most of >my life. Perhaps because of this, I do f

[Python-Dev] Import java classes from python

2014-04-24 Thread Brett Cannon
On Thu Apr 24 2014 at 1:10:39 PM, babu wrote: > Hi, I am new to python. I have a requirement to import java class from > python. Is there any possibility to import java class from python. > This list is for the development *of* Python, not the *use* of Python. But to quickly answer your questio

[Python-Dev] Import java classes from python

2014-04-24 Thread babu
Hi, I am new to python. I have a requirement to import java class from python. Is there any possibility to import java class from python. -- View this message in context: http://python.6.x6.nabble.com/Import-java-classes-from-python-tp5054707.html Sent from the Python - python-dev mailing list

Re: [Python-Dev] pep8 reasoning

2014-04-24 Thread Kristján Valur Jónsson
> -Original Message- > From: Python-Dev [mailto:python-dev- > bounces+kristjan=ccpgames@python.org] On Behalf Of Chris Withers > Sent: 24. apríl 2014 07:18 > To: Python-Dev > Subject: [Python-Dev] pep8 reasoning > The biggest sticking point is naming, particularly as it's the one thin

Re: [Python-Dev] List vs Tuple / Homogeneous vs Heterogeneous / Mutable vs Immutable

2014-04-24 Thread Chris Barker
Ooops, Forgot "reply all" last time -- here it is again. On Wed, Apr 23, 2014 at 3:17 PM, Chris Barker wrote: > On Mon, Apr 21, 2014 at 11:39 PM, Raymond Hettinger < > raymond.hettin...@gmail.com> wrote: > >> In fact, the distinction is extrinsic to their implementations. It is >> only importa

Re: [Python-Dev] pep8 reasoning

2014-04-24 Thread Tim Peters
There's been a bit of serious study on this. The results are still open to interpretation, though ;-) Here's a nice summary: http://whathecode.wordpress.com/2011/02/10/camelcase-vs-underscores-scientific-showdown/ of-course-dashes-are-most-natural-ly y'rs - tim On Thu, Apr 24, 2014 at 11:25 A

Re: [Python-Dev] pep8 reasoning

2014-04-24 Thread Chris Angelico
On Thu, Apr 24, 2014 at 11:59 PM, Barry Warsaw wrote: > I will say this: the original preference for underscore_names in PEP 8 was > spurred by user studies some of our early non-native English speaking users > conducted many years ago. We learned that it was more difficult for many of > them to

Re: [Python-Dev] pep8 reasoning

2014-04-24 Thread Chris Barker - NOAA Federal
One added note: >> if greeting == True: >> if greeting is True: > > This one is based on the preference for identity checks when singletons are > involved, rather than equality tests. Being composed of English words, the > latter is also more readable. It's the same reason why you would do ident

Re: [Python-Dev] pep8 reasoning

2014-04-24 Thread Guido van Rossum
On Thu, Apr 24, 2014 at 7:11 AM, Skip Montanaro wrote: > On Thu, Apr 24, 2014 at 8:59 AM, Barry Warsaw wrote: > > I will say this: the original preference for underscore_names in PEP 8 > was > > spurred by user studies some of our early non-native English speaking > users > > conducted many year

Re: [Python-Dev] pep8 reasoning

2014-04-24 Thread Guido van Rossum
On Wed, Apr 23, 2014 at 11:48 PM, Chris Withers wrote: > Apologies if this is considered off topic, but I'm keen to get the > "language designers" point of view and short of emailing Barry, Guido and > Nick directly, this seemed like the best place. > > I'm having a tough time persuading some peo

Re: [Python-Dev] pep8 reasoning

2014-04-24 Thread Tal Einat
On Thu, Apr 24, 2014 at 4:59 PM, Barry Warsaw wrote: > I will say this: the original preference for underscore_names in PEP 8 was > spurred by user studies some of our early non-native English speaking users > conducted many years ago. We learned that it was more difficult for many of > them to p

Re: [Python-Dev] ref leaks

2014-04-24 Thread Thomas Wouters
On Thu, Apr 24, 2014 at 7:31 AM, Ethan Furman wrote: > On 04/23/2014 09:06 PM, Benjamin Peterson wrote: > >> On Wed, Apr 23, 2014, at 19:14, Ethan Furman wrote: >> >>> Command line: >>> >>> ./python -m test.regrtest -v -R3:3 test_tools >>> >>> Results: >>> >>> Ran 44 tests in 7.628s >>> >

Re: [Python-Dev] ref leaks

2014-04-24 Thread Stefan Krah
Ethan Furman wrote: > >>Any words of wisdom for tracking those leaks? Often the easiest way is to compile --with-valgrind and run the test under Valgrind (obviously). In the Valgrind output, search for "definitely lost" and ignore the rest. If that does not turn up anything, consider a bug in

[Python-Dev] pep8 reasoning

2014-04-24 Thread Chris Withers
Hi All, Apologies if this is considered off topic, but I'm keen to get the "language designers" point of view and short of emailing Barry, Guido and Nick directly, this seemed like the best place. I'm having a tough time persuading some people of the benefits of pep8, particularly when it co

Re: [Python-Dev] pep8 reasoning

2014-04-24 Thread Robert Kern
On 2014-04-24 14:59, Barry Warsaw wrote: I will say this: the original preference for underscore_names in PEP 8 was spurred by user studies some of our early non-native English speaking users conducted many years ago. We learned that it was more difficult for many of them to parse mixedCase nam

Re: [Python-Dev] ref leaks

2014-04-24 Thread Ethan Furman
On 04/23/2014 09:06 PM, Benjamin Peterson wrote: On Wed, Apr 23, 2014, at 19:14, Ethan Furman wrote: Command line: ./python -m test.regrtest -v -R3:3 test_tools Results: Ran 44 tests in 7.628s OK (skipped=1) . test_tools leaked [0, 2, 2] references, sum=4 1 test faile

Re: [Python-Dev] pep8 reasoning

2014-04-24 Thread Skip Montanaro
On Thu, Apr 24, 2014 at 8:59 AM, Barry Warsaw wrote: > I will say this: the original preference for underscore_names in PEP 8 was > spurred by user studies some of our early non-native English speaking users > conducted many years ago. We learned that it was more difficult for many of > them to p

Re: [Python-Dev] pep8 reasoning

2014-04-24 Thread Barry Warsaw
On Apr 24, 2014, at 08:18 AM, Chris Withers wrote: >I'm having a tough time persuading some people of the benefits of pep8, >particularly when it comes to applying to an existing large code base. First of all, the purposes of PEP 8 is not to impose mandates of style on your colleagues. :) Two im

Re: [Python-Dev] pep8 reasoning

2014-04-24 Thread Tim Golden
On 24/04/2014 12:59, Tal Einat wrote: > As far as I know that reason for these examples being frowned upon is > that they are needlessly redundant. Oh, the irony! (Sorry, couldn't resist) TJG ___ Python-Dev mailing list Python-Dev@python.org https://ma

Re: [Python-Dev] pep8 reasoning

2014-04-24 Thread Tal Einat
On Thu, Apr 24, 2014 at 10:18 AM, Chris Withers wrote: > A couple of others that have raised some consternation; what are the > technical reasons for this pattern being bad: > > if len(seq) > if not len(seq) > > ...or, for me, the rather ugly: > > if 0 != len(seq) > > Likewise, these: > > if greet

Re: [Python-Dev] pep8 reasoning

2014-04-24 Thread Skip Montanaro
On Thu, Apr 24, 2014 at 2:18 AM, Chris Withers wrote: > What were the compelling reasons to go from mixedCase to > underscore_separated? What's considered the best approach for migrating from > the former to the latter? I never recall Python "going from" camelCase to separate_words. The descripti

[Python-Dev] pep8 reasoning

2014-04-24 Thread Chris Withers
Hi All, Apologies if this is considered off topic, but I'm keen to get the "language designers" point of view and short of emailing Barry, Guido and Nick directly, this seemed like the best place. I'm having a tough time persuading some people of the benefits of pep8, particularly when it co