Whether this question is necessary actually depends on the nature of the project. Generally speaking, there will be both, and it is best to have both.

setup.pyThis file is used to manage modules. You can package your project as a module and upload it to pypi. You can also put the project as a module into the python system loading module directory.

requiremens.txtThis file lists the non-project dependencies that your project references. Other than that, it has no other function.

Therefore, it can be seen that there is no conflict between these two projects, and there is a great need to coexist.

• It is essential if your project needs to be saved as a system module or can be installed as a system commandsetup.py

• If your project can be run directly, thenrequirements.txtis also essential.

• If you need both functions, then both files must be included.

Do you need both functions?

There must be one, and there are many more. For example, Flask supports two methods:

• Start as a system command. A new Click package has been added in Flask 0.11.1, which allows you to run it as a command after setup

• Direct operation, traditionalFlask启动方式一般就是app.run()或者python manage.py runserver

Hope it’s helpful to the questioner.

---

Added:

In fact,setup.py里面也会有依赖的列表，所以，在 setup 的时候无需担心会和requirements.txt关联，因为不需要关联这个，作者已经在setup.pywill also have a list of dependencies, so there is no need to worry about being associated with

during setup, because there is no need to associate this, the author has already written it in .

I saw that requirements.txt is a must. It declares which third-party libraries are introduced into your project. As a flask web application setup.py doesn't seem to make sense. . .

setup.py是安装你自己写的模块，一般依靠执行sudo python setup.py install,

requirements.txt是指明这个模块所依赖的模块，一般执行sudo pip install -r requirements.txtTo install dependent modules.