推荐学习书目
› Learn Python the Hard Way
Python Sites
› PyPI - Python Package Index
› http://diveintopython.org/toc/index.html
› Pocoo
值得关注的项目
› PyPy
› Celery
› Jinja2
› Read the Docs
› gevent
› pyenv
› virtualenv
› Stackless Python
› Beautiful Soup
› 结巴中文分词
› Green Unicorn
› Sentry
› Shovel
› Pyflakes
› pytest
Python 编程
› pep8 Checker
Styles
› PEP 8
› Google Python Style Guide
› Code Style from The Hitchhiker's Guide
apeshit
V2EX  ›  Python

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

  •  
  •   apeshit · Jan 7, 2019 · 5442 views
    This topic created in 2870 days ago, the information mentioned may be changed or developed.

    想请问 v2er 知不知道 python 有没有类似这样的开发规范手册? 里面包含了开发技巧,和大企业里面的规约 之类的.

    楼主自己读过 java 的开发手册, 没事就会翻一翻,像参考书一样很有用, 如果 python 也有就好了

    19 replies  •  2019-01-18 13:55:03 +08:00
    haoz1w0w
    haoz1w0w
    Jan 7, 2019
    2
    有人会按照那个开发规范开发么。。。
    lihongjie0209
    lihongjie0209
    Jan 7, 2019
    4
    Python 社区要的是自由和优雅, 手册这么死板的东西是不可能的
    PhpBestRubbish
    PhpBestRubbish
    Jan 7, 2019
    5
    自由和优雅,对于企业级多人开发来说不是灾难吗?
    alexmy
    alexmy
    Jan 7, 2019
    6
    我欲成仙,我只想写 a,b,c,d 的变量名。
    Raisu
    Raisu
    Jan 7, 2019
    7
    用 pycharm 的话,默认会有 pep-0008 风格提示的,只要没有提醒那应该就 OK 了
    qq976739120
    qq976739120
    Jan 7, 2019
    8
    忘掉所有乱七八糟的语法糖
    longaiwp
    longaiwp
    Jan 7, 2019❤️1
    9
    如果选择忘掉乱七八糟的语法糖,那我为什么不用 Jawa ?
    KMpAn8Obw1QhPoEP
    KMpAn8Obw1QhPoEP
    Jan 7, 2019 via Android
    10
    不懂 Java 也不懂 Python 只写过几行 hello world 级别的垃圾代码
    感觉 Java 好啰嗦
    Python 又不好好说话
    tiedan
    tiedan
    Jan 7, 2019
    11
    用 pep8 作为参考就行了
    chroming
    chroming
    Jan 7, 2019
    12
    就谷歌那个吧
    shmilypeter
    shmilypeter
    Jan 7, 2019
    13
    那不是开发手册,那是代码规范
    smdbh
    smdbh
    Jan 7, 2019
    14
    @Raisu alt f8 ?
    gitandgit
    gitandgit
    Jan 7, 2019 via iPad
    15
    KgM4gLtF0shViDH3
    KgM4gLtF0shViDH3
    Jan 8, 2019 via iPhone
    16
    自从 py 被培训班盯上之后半吊子越来越多,招人筛选难度也越来越大
    passerbytiny
    passerbytiny
    Jan 8, 2019
    17
    作为 Java 开发,我已经很久没看过那个开发手册了。

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

    阿里那个手册,当你在阿里,或者想去阿里的时候,才是参考手册;否则就只是个参考,不是手册。
    lazyfighter
    lazyfighter
    Jan 8, 2019
    18
    @passerbytiny 参考也不错,小公司没有规范的遍地都是。
    iorilu
    iorilu
    Jan 18, 2019
    19
    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!
    About   ·   Help   ·   Advertise   ·   Blog   ·   API   ·   FAQ   ·   Privacy   ·   Solana   ·   4440 Online   Highest 6679   ·     Select Language
    创意工作者们的社区
    World is powered by solitude
    VERSION: 3.9.8.5 · 169ms · UTC 08:14 · PVG 16:14 · LAX 00:14 · JFK 03:14
    ♥ Do have faith in what you're doing.