有没有类似阿里巴巴 Java 开发手册一样的 Python 开发手册?

有人会按照那个开发规范开发么。。。

Python 社区要的是自由和优雅, 手册这么死板的东西是不可能的

自由和优雅，对于企业级多人开发来说不是灾难吗？

我欲成仙，我只想写 a,b,c,d 的变量名。

用 pycharm 的话，默认会有 pep-0008 风格提示的，只要没有提醒那应该就 OK 了

忘掉所有乱七八糟的语法糖

如果选择忘掉乱七八糟的语法糖，那我为什么不用 Jawa ？

不懂 Java 也不懂 Python 只写过几行 hello world 级别的垃圾代码
感觉 Java 好啰嗦
Python 又不好好说话

用 pep8 作为参考就行了

就谷歌那个吧

那不是开发手册，那是代码规范

@Raisu alt f8 ？

自从 py 被培训班盯上之后半吊子越来越多，招人筛选难度也越来越大

作为 Java 开发，我已经很久没看过那个开发手册了。

所谓的规范，是团队合作用的，那么自然团队不同，规范也就不同。

阿里那个手册，当你在阿里，或者想去阿里的时候，才是参考手册；否则就只是个参考，不是手册。

@passerbytiny 参考也不错，小公司没有规范的遍地都是。

import this

The Zen of Python, by Tim Peters

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!