Linux unitednationsplay.com 3.10.0-1160.45.1.el7.x86_64 #1 SMP Wed Oct 13 17:20:51 UTC 2021 x86_64
nginx/1.20.1
Server IP : 188.130.139.92 & Your IP : 18.117.106.206
Domains :
Cant Read [ /etc/named.conf ]
User : web
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
usr /
share /
doc /
python3-setuptools-39.2.0 /
Delete
Unzip
Name
Size
Permission
Date
Action
CHANGES.rst
110.95
KB
-rw-r--r--
2018-05-19 19:18
README.rst
1.51
KB
-rwxr-xr-x
2018-05-19 19:18
developer-guide.txt
5.41
KB
-rw-r--r--
2018-05-19 19:18
development.txt
1.44
KB
-rw-r--r--
2018-05-19 19:18
easy_install.txt
73.58
KB
-rw-r--r--
2018-05-19 19:18
formats.txt
30.49
KB
-rw-r--r--
2018-05-19 19:18
history.txt
1.84
KB
-rw-r--r--
2018-05-19 19:18
index.txt
537
B
-rw-r--r--
2018-05-19 19:18
pkg_resources.txt
91.4
KB
-rw-r--r--
2018-05-19 19:18
python3.txt
3.87
KB
-rw-r--r--
2018-05-19 19:18
releases.txt
2.4
KB
-rw-r--r--
2018-05-19 19:18
requirements.txt
61
B
-rw-r--r--
2018-05-19 19:18
roadmap.txt
167
B
-rw-r--r--
2018-05-19 19:18
setuptools.txt
125.23
KB
-rw-r--r--
2018-05-19 19:18
Save
Rename
------------------------- Development on Setuptools ------------------------- Setuptools is maintained by the Python community under the Python Packaging Authority (PyPA) and led by Jason R. Coombs. This document describes the process by which Setuptools is developed. This document assumes the reader has some passing familiarity with *using* setuptools, the ``pkg_resources`` module, and EasyInstall. It does not attempt to explain basic concepts like inter-project dependencies, nor does it contain detailed lexical syntax for most file formats. Neither does it explain concepts like "namespace packages" or "resources" in any detail, as all of these subjects are covered at length in the setuptools developer's guide and the ``pkg_resources`` reference manual. Instead, this is **internal** documentation for how those concepts and features are *implemented* in concrete terms. It is intended for people who are working on the setuptools code base, who want to be able to troubleshoot setuptools problems, want to write code that reads the file formats involved, or want to otherwise tinker with setuptools-generated files and directories. Note, however, that these are all internal implementation details and are therefore subject to change; stick to the published API if you don't want to be responsible for keeping your code from breaking when setuptools changes. You have been warned. .. toctree:: :maxdepth: 1 developer-guide formats releases