faraday/setup.py at master · dominico120/faraday

Repository navigation

History

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

177

178

179

180

181

182

183

184

185

186

187

188

189

190

191

192

193

194

195

196

197

198

199

200

201

202

203

204

205

206

207

208

209

210

211

212

213

214

215

216

217

218

219

220

221

222

223

224

225

226

227

228

229

230

231

232

233

234

235

236

237

238

239

240

241

242

243

244

245

246

247

248

"""A setuptools based setup module.

See:

https://packaging.python.org/en/latest/distributing.html

https://github.com/pypa/sampleproject

"""

# Always prefer setuptools over distutils

from setuptools import setup, find_packages

# io.open is needed for projects that support Python 2.7

# It ensures open() defaults to text mode with universal newlines,

# and accepts an argument to specify th 8000 e text encoding

# Python 3 only projects can skip this import

from re import search

with open('faraday/__init__.py', encoding='utf8') as f:

version = search(r'__version__ = \'(.*?)\'', f.read()).group(1)

# Taken from https://stackoverflow.com/questions/14399534/reference-requirements-txt-for-the-install-requires-kwarg-in-setuptools-setup-py/14399775#14399775

with open('requirements.txt') as fp:

required = fp.read().splitlines()

with open('requirements_dev.txt') as fp:

dev_required = fp.read().splitlines()

with open("README.md") as readme_file:

readme = readme_file.read()

try:

# When setuptools_scm is installed, it ignores the MANIFEST.in contents,

# so a developer won't notice the MANIFEST.in includes are incomplete.

# This can make some user bugs irrepoducible in a dev environment,

# and we don't want this!

# Taken from https://github.com/pypa/setuptools_scm/issues/190#issuecomment-351181286

import setuptools_scm.integration

setuptools_scm.integration.find_files = lambda _: []

except ImportError:

pass

# Arguments marked as "Required" below must be included for upload to PyPI.

# Fields marked as "Optional" may be commented out.

setup(

# This is the name of your project. The first time you publish this

# package, this name will be registered for you. It will determine how

# users can install this project, e.g.:

# $ pip install sampleproject

# And where it will live on PyPI: https://pypi.org/project/sampleproject/

# There are some restrictions on what makes a valid project name

# specification here:

# https://packaging.python.org/specifications/core-metadata/#name

name='faradaysec', # Required

# Versions should comply with PEP 440:

# https://www.python.org/dev/peps/pep-0440/

# For a discussion on single-sourcing the version across setup.py and the

# project code, see

# https://packaging.python.org/en/latest/single_source_version.html

version=version, # Required

# This is a one-line description or tagline of what your project does. This

# corresponds to the "Summary" metadata field:

# https://packaging.python.org/specifications/core-metadata/#summary

description='Open Source Collaborative Penetration Test and Vulnerability Management '

'Platform https://www.faradaysec.com', # Optional

# This is an optional longer description of your project that represents

# the body of text which users will see when they visit PyPI.

# Often, this is the same as your README, so you can just read it in from

# that file directly (as we have already done above)

# This field corresponds to the "Description" metadata field:

# https://packaging.python.org/specifications/core-metadata/#description-optional

long_description=readme, # Optional

long_description_content_type='text/markdown',

# Denotes that our long_description is in Markdown; valid values are

# text/plain, text/x-rst, and text/markdown

# Optional if long_description is written in reStructuredText (rst) but

# required for plain-text or Markdown; if unspecified, "applications should

# attempt to render [the long_description] as text/x-rst; charset=UTF-8 and

# fall back to text/plain if it is not valid rst" (see link below)

# This field corresponds to the "Description-Content-Type" metadata field:

# https://packaging.python.org/specifications/core-metadata/#description-content-type-optional

# long_description_content_type='text/markdown', # Optional (see note above)

# This should be a valid link to your project's main homepage.

# This field corresponds to the "Home-Page" metadata field:

# https://packaging.python.org/specifications/core-metadata/#home-page-optional

url='https://github.com/infobyte/faraday', # Optional

# This should be your name or the name of the organization which owns the

# project.

author='Faradaysec', # Optional

# This should be a valid email address corresponding to the author listed

# above.

author_email='devel@faradaysec.com', # Optional

# Classifiers help users find your project by categorizing it.

# For a list of valid classifiers, see https://pypi.org/classifiers/

classifiers=[ # Optional

# How mature is this project? Common values are

# 3 - Alpha

# 4 - Beta

# 5 - Production/Stable

'Development Status :: 5 - Production/Stable',

# Indicate who your project is intended for

'Intended Audience :: Information Technology',

'Intended Audience :: System Administrators',

'Topic :: Security',

'Topic :: Software Development :: Bug Tracking',

'Topic :: Software Development :: Quality Assurance',

'Topic :: System :: Networking :: Monitoring',

# Pick your license as you wish

'License :: OSI Approved :: GNU General Public License v3 (GPLv3)',

# Specify the Python versions you support here. In particular, ensure

# that you indicate whether you support Python 2, Python 3 or both.

# These classifiers are *not* checked by 'pip install'. See instead

# 'python_requires' below.

'Programming Language :: Python :: 3',

'Programming Language :: Python :: 3.7',

'Programming Language :: Python :: 3.8',

'Programming Language :: Python :: 3.9',

# This field adds keywords for your project which will appear on the

# project page. What does your project relate to?

# Note that this is a string of words separated by whitespace, not a list.

keywords='security tools', # Optional

# You can just specify package directories manually here if your project is

# simple. Or you can use find_packages().

# Alternatively, if you just want to distribute a single Python file, use

# the `py_modules` argument instead as follows, which will expect a file

# called `my_module.py` to exist:

# py_modules=["my_module"],

# packages=find_packages(exclude=['contrib', 'docs', 'tests']), # Required

# packages=[''],

# packages=['faraday', 'faraday.server', 'faraday.utils'],

# packages=['faraday.' + package

# for package in find_packages(

# '.', include=['server.*', 'config.*', 'utils.*', 'client.*',

# 'server', 'config', 'utils', 'client'])

# ] + ['faraday'],

# package_dir={'faraday': '.'},

packages=find_packages(include=['faraday', 'faraday.*']),

# Specify which Python versions you support. In contrast to the

# 'Programming Language' classifiers above, 'pip install' will check this

# and refuse to install the project if the version does not match. If you

# do not support Python 2, you can simplify this to '>=3.5' or similar, see

# https://packaging.python.org/guides/distributing-packages-using-setuptools/#python-requires

# Do not use `*` in the python_requires version format

python_requires='>=3.7',

# This field lists other packages that your project depends on to run.

# Any package you put here will be installed by pip when your project is

# installed, so they must be valid existing projects.

# For an analysis of "install_requires" vs pip's requirements files see:

# https://packaging.python.org/en/latest/requirements.html

install_requires=required, # Optional

# List additional groups of dependencies here (e.g. development

# dependencies). Users will be able to install these using the "extras"

# syntax, for example:

# $ pip install sampleproject[dev]

# Similar to `install_requires` above, these must be valid existing

# projects.

extras_require={ # Optional

'dev': ['check-manifest'],

'test': ['coverage'],

# If there are data files included in your packages that need to be

# installed, specify them here.

# If using Python 2.6 or earlier, then these have to be included in

# MANIFEST.in as well.

include_package_data=True,

package_data={ # Optional

'': ['requirements.txt', ],

# Although 'package_data' is the preferred approach, in some case you may

# need to place data files outside of your packages. See:

# http://docs.python.org/3.4/distutils/setupscript.html#installing-additional-files

# In this case, 'data_file' will be installed into '<sys.prefix>/my_data'

# data_files=[('my_data', ['data/data_file'])], # Optional

# To provide executable scripts, use entry points in preference to the

# "scripts" keyword. Entry points provide cross-platform support and allow

# `pip` to create the appropriate form of executable for the target

# platform.

# For example, the following would provide a command called `sample` which

# executes the function `main` from this package when invoked:

entry_points={ # Optional

'console_scripts': [

'faraday-server=faraday.start_server:main',

'faraday-manage=faraday.manage:cli',

'faraday-worker=faraday.server.celery_worker:main',

'faraday-worker-gevent=faraday.server.celery_worker_gevent:main',

'faraday-start-all=faraday.start_all:main'

# List additional URLs that are relevant to your project as a dict.

# This field corresponds to the "Project-URL" metadata fields:

# https://packaging.python.org/specifications/core-metadata/#project-url-multiple-use

# Examples listed include a pattern for specifying where the package tracks

# issues, where the source is hosted, where to say thanks to the package

# maintainers, and where to support the project financially. The key is

# what's used to render the link text on PyPI.

project_urls={ # Optional

'Bug Reports': 'https://github.com/infobyte/faraday/issues',

'Say Thanks!': 'http://saythanks.io/to/faradaysec',

'Source': 'https://github.com/infobyte/faraday/',

setup_requires=['pytest-runner'],

tests_require=dev_required,

)

FilesExpand file tree

setup.py

Latest commit

History

setup.py

File metadata and controls