Python第二课——Python包安装以及代码规范

文章介绍了如何使用pip管理Python包,包括切换虚拟环境、安装、升级和卸载包,以及处理pip更新问题。此外,还强调了Python编码规范如PEP8,并推荐了Autopep8工具进行代码格式化,以及如何在PyCharm中集成该工具。最后,提到了Python变量的命名约定和类的命名规范。
摘要由CSDN通过智能技术生成

PIP包管理工具
切换至python虚拟环境脚本处执行PIP——例如:cd venv/Scripts目录执行
pip -V 显示当前pip版本
pip help[install] 查看install命令的帮助手册
pip install xxx 安装软件包
pip install xxx==2.2.6 安装指定版本的包
pip download xxx 下载软件包
pip uninstall xxx 卸载软件包
pip list 查看系统已安装包
pip list -o 查看可升级的软件包
pip install -U pip 对pip进行升级
pip show xxx 显示安装包信息

  • pip更新问题:
    在这里插入图片描述
    这个时候老PIP卸载了,新PIP未装成功;无法使用PIP命令;此时可以使用esay_install.exe pip命令安装pip;安装完成为最新版本pip
    (cmd:依次输入一下两条命令:
    curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py
    python get-pip.py)
    使用国内下载源安装:pip install requests -i http://mirrors.aliyun.com/pypi/simple/
    配置国内镜像:
    1)linux:/.pip/pip.con
    windows:运行窗口直接%homepath%,新建pip文件夹,文件夹中新建pip.ini文件(index-url为镜像地址)
    在这里插入图片描述
    2)Scripts脚本中直接拼写pip config set global.index-url xxx xxx为国内镜像源地址
    pip config list 查看配置镜像源

Python编码规范:PEP 8、Google风格、Pocoo风格
安装代码格式化工具:Autopep8
Autopep8 是一个将python代码自动排版为PEP 8风格的小工具。它使用PEP 8工具来决定代码中的哪部分需要被排版
打开终端,使用pip 命令安装Autopep8:pip install autopep8
终端为python安装目录的scripts目录下安装,不然运行会报错
autopep8是一个命令行工具,可以对某个文件进行代码格式化,命令如下:

autopep8 --in-place --aggressive --aggressive <filename>

终端安装完后,Pycharm IDE配置集成Autopep 8:
PyCharm 配置 Autopep8 方法如下:
1)选择菜单「File」–>「Settings」–>「Tools」–>「External Tools」–>点击加号添加工具
2)Name:Autopep8 (可随意填写)
Tools settings:
Programs:autopep8
Parameters:--in-place --aggressive --aggressive $FilePath$
Working directory:$ProjectFileDir$
3)选择菜单「Tool」–>「Extern Tools」–>「Autopep8」或在某个文件中右键选择「Extern Tools」–>
「Autopep8」,即可使用autopep8自动格式化你的Python代码

Python常用编码规范:

Python中定义变量:
xx:			公有变量
_xx:		单前置下划线,私有化属性或方法,类对象和子类可以访问
__xx:		双前置下划线,私有化属性或方法,无法在外部直接访问
__xx__:		双前后下划线,系统定义名称
xx_:		单后置下划线,用于避免python关键字的冲突

类的命名使用驼峰大小写;常量应用大写字母定义常量

阅读者体验>编程者体验>机器的体验

  • 0
    点赞
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
This is Python version 3.1.5 ============================ Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012 Python Software Foundation. All rights reserved. Python 3.x is a new version of the language, which is incompatible with the 2.x line of releases. The language is mostly the same, but many details, especially how built-in objects like dictionaries and strings work, have changed considerably, and a lot of deprecated features have finally been removed. Build Instructions ------------------ On Unix, Linux, BSD, OSX, and Cygwin: ./configure make make test sudo make install This will install Python as python3. You can pass many options to the configure script; run "./configure --help" to find out more. On OSX and Cygwin, the executable is called python.exe; elsewhere it's just python. On Mac OS X, if you have configured Python with --enable-framework, you should use "make frameworkinstall" to do the installation. Note that this installs the Python executable in a place that is not normally on your PATH, you may want to set up a symlink in /usr/local/bin. On Windows, see PCbuild/readme.txt. If you wish, you can create a subdirectory and invoke configure from there. For example: mkdir debug cd debug ../configure --with-pydebug make make test (This will fail if you *also* built at the top-level directory. You should do a "make clean" at the toplevel first.) What's New ---------- We try to have a comprehensive overview of the changes in the "What's New in Python 3.1" document, found at http://docs.python.org/3.1/whatsnew/3.1.html For a more detailed change log, read Misc/NEWS (though this file, too, is incomplete, and also doesn't list anything merged in from the 2.7 release under development). If you want to install multiple versions of Python see the section below entitled "Installing multiple versions". Documentation ------------- Documentation for Python 3.1 is online, updated twice a day: http://docs.python.org/3.1/ All documentation is also available online at the Python web site (http://docs.python.org/, see below). It is available online for occasional reference, or can be downloaded in many formats for faster access. The documentation is downloadable in HTML, PostScript, PDF, LaTeX (through 2.5), and reStructuredText (2.6+) formats; the LaTeX and reStructuredText versions are primarily for documentation authors, translators, and people with special formatting requirements. Converting From Python 2.x to 3.x --------------------------------- Python starting with 2.6 will contain features to help locating code that needs to be changed, such as optional warnings when deprecated features are used, and backported versions of certain key Python 3.x features. A source-to-source translation tool, "2to3", can take care of the mundane task of converting large amounts of source code. It is not a complete solution but is complemented by the deprecation warnings in 2.6. See http://docs.python.org/py3k/library/2to3.html for more information. Testing ------- To test the interpreter, type "make test" in the top-level directory. This runs the test set twice (once with no compiled files, once with the compiled files left by the previous test run). The test set produces some output. You can generally ignore the messages about skipped tests due to optional features which can't be imported. If a message is printed about a failed test or a traceback or core dump is produced, something is wrong. On some Linux systems (those that are not yet using glibc 6), test_strftime fails due to a non-standard implementation of strftime() in the C library. Please ignore this, or upgrade to glibc version 6. By default, tests are prevented from overusing resources like disk space and memory. To enable these tests, run "make testall". IMPORTANT: If the tests fail and you decide to mail a bug report, *don't* include the output of "make test". It is useless. Run the failing test manually, as follows: ./python Lib/test/regrtest.py -v test_whatever (substituting the top of the source tree for '.' if you built in a different directory). This runs the test in verbose mode. Installing multiple versions ---------------------------- On Unix and Mac systems if you intend to install multiple versions of Python using the same installation prefix (--prefix argument to the configure script) you must take care that your primary python executable is not overwritten by the installation of a different version. All files and directories installed using "make altinstall" contain the major and minor version and can thus live side-by-side. "make install" also creates ${prefix}/bin/python3 which refers to ${prefix}/bin/pythonX.Y. If you intend to install multiple versions using the same prefix you must decide which version (if any) is your "primary" version. Install that version using "make install". Install all other versions using "make altinstall". For example, if you want to install Python 2.5, 2.6 and 3.0 with 2.6 being the primary version, you would execute "make install" in your 2.6 build directory and "make altinstall" in the others. Issue Tracker and Mailing List ------------------------------ We're soliciting bug reports about all aspects of the language. Fixes are also welcome, preferable in unified diff format. Please use the issue tracker: http://bugs.python.org/ If you're not sure whether you're dealing with a bug or a feature, use the mailing list: python-dev@python.org To subscribe to the list, use the mailman form: http://mail.python.org/mailman/listinfo/python-dev/ Proposals for enhancement ------------------------- If you have a proposal to change Python, you may want to send an email to the comp.lang.python or python-ideas mailing lists for inital feedback. A Python Enhancement Proposal (PEP) may be submitted if your idea gains ground. All current PEPs, as well as guidelines for submitting a new PEP, are listed at http://www.python.org/dev/peps/. Release Schedule ---------------- See PEP 375 for release details: http://www.python.org/dev/peps/pep-0375/ Copyright and License Information --------------------------------- Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Python Software Foundation. All rights reserved. Copyright (c) 2000 BeOpen.com. All rights reserved. Copyright (c) 1995-2001 Corporation for National Research Initiatives. All rights reserved. Copyright (c) 1991-1995 Stichting Mathematisch Centrum. All rights reserved. See the file "LICENSE" for information on the history of this software, terms & conditions for usage, and a DISCLAIMER OF ALL WARRANTIES. This Python distribution contains *no* GNU General Public License (GPL) code, so it may be used in proprietary projects. There are interfaces to some GNU code but these are entirely optional. All trademarks referenced herein are property of their respective holders.
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值