News for hackers. Stuff that matters.

A comment on Making Python 3 more attractive. Parent comment

Re:Making Python 3 more attractive by plesner on Wednesday April 15, 2015 @03:45AM (#9379425)
To what end though? It's a small thing sure but it's busywork. Why am I being asked to do busywork?
[ Parent | on HN ]
Re:Making Python 3 more attractive by raverbashing on Wednesday April 15, 2015 @04:24AM (#9379547)
Yeah, I don't like the busywork that Pep8 makes me do it, and it's a lot, and some of it is stupid, but it has to be done

You certainly don't have to do it if you don't want Python 3 and 2to3 makes it a lot easier

[ Parent | on HN ]
Re:Making Python 3 more attractive by coldtea on Wednesday April 15, 2015 @04:50AM (#9379642)
>Yeah, I don't like the busywork that Pep8 makes me do it, and it's a lot, and some of it is stupid, but it has to be done

Actually no, it hasn't. PEP8 is just a formatting standard, your code will work with your own standard too.

[ Parent | on HN ]
Re:Making Python 3 more attractive by raverbashing on Wednesday April 15, 2015 @05:22AM (#9379776)
True, I meant this https://pypi.python.org/pypi/pep8
[ Parent | on HN ]
Re:Making Python 3 more attractive by alexchamberlain on Wednesday April 15, 2015 @05:59AM (#9379895)
Guido doesn't like that tool; they're guidelines, not rules.
[ Parent | on HN ]
Re:Making Python 3 more attractive by raverbashing on Wednesday April 15, 2015 @06:19AM (#9379960)
> Guido doesn't like that tool; they're guidelines, not rules.

Yes, a lot of people need to get that memo

I don't like it as well, but it keeps a group of developers in check. And it can be configured, so there's that as well

Too bad autopep8 produces bad results out of the box

[ Parent | on HN ]