Project Name:
Pigar
Project Address:
Https://github.com/damnever/pigar
Instructions for use:
USAGE: PIGAR [-H] [-V] [-U] [-S NAME [NAME&NBSP, ...] [-c [PATH]] [-l LOG_LEVEL]    [-I DIR [DIR&NBSP, ...] [-p save_path] [-p project_path]python requirements tool -- pigar, it will do only one thing at each time. Default action is generate requirements.txt in current directory.optional arguments: -h, --help show this help message and exit -v, --version show pigar version information and exit -u, -- update update database, use it when pigar failed you, exit when        ACTION DONE  -S NAME [NAME&NBSP, ...] search package name by import name, use it if you do not know import name come from which package, exit when action done -c [PATH] check requirements for the latest version. If file path not given, search *requirements.txt in current directory, if not found, generate file requirements.txt, exit when action done -l LOG_LEVEL show given level log messages, argument can be ( error, warning, info), case-insensitive -i dir [dir &NBSP, ...] given a list of directory to ignore, relative Directory, *used for* -c and default action -p SAVE_PATH save requirements in given file path, *used for* default action -P PROJECT_PATH project path, which is directory, *used for* default action
There are pictures and phases:
650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M01/87/FD/wKiom1fmFO-T8JltAAA0s4vDHu8383.png "title=" Pigar.png "alt=" Wkiom1fmfo-t8jltaaa0s4vdhu8383.png "/>
Note: If you run into someone else's project when you encounter "import Error:xxx", then you can like the artifact Pigar to search the project in the import name in the end from which the installation package, in reading other people's source code is also very useful.
This article is from the "ζ Automated operation and maintenance development Road ζ" blog, please be sure to keep this source http://xmdevops.blog.51cto.com/11144840/1856062
development tool _pigar. Quickly generate dependent file Requirements.txt for Python projects?