Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #73935 > unrolled thread
| Started by | Demian Brecht <demianbrecht@gmail.com> |
|---|---|
| First post | 2014-07-03 20:23 -0700 |
| Last post | 2014-07-03 20:23 -0700 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: PEP8 and 4 spaces Demian Brecht <demianbrecht@gmail.com> - 2014-07-03 20:23 -0700
| From | Demian Brecht <demianbrecht@gmail.com> |
|---|---|
| Date | 2014-07-03 20:23 -0700 |
| Subject | Re: PEP8 and 4 spaces |
| Message-ID | <mailman.11479.1404444230.18130.python-list@python.org> |
[Multipart message — attachments visible in raw view] — view raw
On Jul 3, 2014 10:31 AM, "Tobiah" <tshepard@rcsreg.com> wrote: > Just need ammo for when the hammer of code unification comes down. One issue that I've encountered in the past (one of the reasons outside of pep8) that I switched to spaces is when working with libraries other than your own. If you want to stick print statements, breakpoints or make any other modifications to the code you're working with, chances are if you're using tabs in your editor, you're going to run into issues when making those changes. Most (of not all) libraries I've worked with use spaces. Pep8 suggests the use of spaces. New hires who have spent any amount of time in python are /likely/ most used to using spaces. For those reasons I much prefer spaces over tabs.
Back to top | Article view | comp.lang.python
csiph-web