dtomicek/Packaging
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

formatting

Browse Source
This commit is contained in:
David Tomicek
2021-07-12 12:58:58 +02:00
parent 8bffb75c6b
commit be5dcaa128
1 changed files with 287 additions and 287 deletions
Download Patch File Download Diff File Expand all files Collapse all files

574
README.md
View File

@@ -29,11 +29,11 @@ If you (for some reason) want to uninstall this project just type this:
- sudo apt-get remove server22 -y - sudo apt-get remove server22 -y
## SERVER22 info ## Server22 info
Server22 is single module, which creates a socket and waits for the connection of client. Server22 is single module, which creates a socket and waits for the connection of client.
## Trees: ## Trees:
root dir where installation is applied root dir where installation is applied:
├── DEBIAN ├── DEBIAN
│   └── control │   └── control
@@ -47,44 +47,44 @@ root dir where installation is applied
├── __init__.py ├── __init__.py
└── server22.py └── server22.py
- dir created after installation: dir created after installation:
├── DEBIAN ├── DEBIAN
│   └── control │   └── control
└── usr └── usr
├── bin ├── bin
│   └── server22 │   └── server22
├── lib ├── lib
│   └── python3 │   └── python3
│   └── dist-packages │   └── dist-packages
│   ├── server22 │   ├── server22
│   │   ├── __init__.py │   │   ├── __init__.py
│   │   └── server22.py │   │   └── server22.py
│   └── server22-2.2.2.egg-info │   └── server22-2.2.2.egg-info
│   ├── dependency_links.txt │   ├── dependency_links.txt
│   ├── entry_points.txt │   ├── entry_points.txt
│   ├── PKG-INFO │   ├── PKG-INFO
│   └── top_level.txt │   └── top_level.txt
└── share └── share
└── doc └── doc
└── server22 └── server22
├── copyright ├── copyright
└── changelog.gz └── changelog.gz
## setup.py ## setup.py
setup.py in root folder is ESSENTIAL! In this project is used the bare minimum of it: setup.py in root folder is ESSENTIAL! In this project is used the bare minimum of it:
#!/usr/bin/python #!/usr/bin/python
from setuptools import setup from setuptools import setup
setup( setup(
name='server22', name='server22',
version='2.2.2', version='2.2.2',
description='Start a server, which listens on port 5000', description='Start a server, which listens on port 5000',
long_description='Server waits on client to join on localhost:5000.', long_description='Server waits on client to join on localhost:5000.',
packages=['server22'], packages=['server22'],
package_dir={'':'src'}, package_dir={'':'src'},
entry_points={"console_scripts": ["server22 = server22.server22:main"]}, entry_points={"console_scripts": ["server22 = server22.server22:main"]},
) )
You can find all possibilities and options of setup.py down below. You can find all possibilities and options of setup.py down below.
@@ -99,18 +99,18 @@ Nowadays directory should be named /DEBIAN with capital letters and It is enough
dpkg will read the instructions and pack that to .deb dpkg will read the instructions and pack that to .deb
This is how It looks like: This is how It looks like:
Source: server22 Source: server22
Maintainer: commrat <something@hotmail.com> Maintainer: commrat <something@hotmail.com>
Section: python Section: python
Priority: optional Priority: optional
Build-Depends: python3.8, dh-python, python3-setuptools, python3-all, debhelper (>= 9) Build-Depends: python3.8, dh-python, python3-setuptools, python3-all, debhelper (>= 9)
Depends: python3, python-docopt Depends: python3, python-docopt
Standards-Version: 3.9.6 Standards-Version: 3.9.6
Version: 13.2.2 Version: 13.2.2
Package: server22 Package: server22
Architecture: all Architecture: all
Description: Start a server, which listens on port 5000 Description: Start a server, which listens on port 5000
And listens. And listens.
NOTE: third party library docopt should be installed by pip to be functional in dpkg packaging. NOTE: third party library docopt should be installed by pip to be functional in dpkg packaging.
@@ -122,7 +122,7 @@ make some files You need (for example Pipfile, README, etc.)
Shell script, which automatized the process of installation and packaging. Shell script, which automatized the process of installation and packaging.
You can find more info about tasks performed in install.sh - comments. You can find more info about tasks performed in install.sh - comments.
## python setup.py <args> ## python setup.py
For the long time, distutils was the most used library for python installations, however official Python Software Foundation For the long time, distutils was the most used library for python installations, however official Python Software Foundation
does not recommend this lib anymore. does not recommend this lib anymore.
setuptools were created and It offers more options, after making setuptools implemented in python installation It becomes standart. setuptools were created and It offers more options, after making setuptools implemented in python installation It becomes standart.
@@ -131,70 +131,70 @@ Now we will take a look for some python setup.py use cases.
* python setup.py build * python setup.py build
Creates a build folder (which is necessary for installation) - but not actually install anything. We can think about that as some 'preparation for install'. Creates a build folder (which is necessary for installation) - but not actually install anything. We can think about that as some 'preparation for install'.
tree: tree:
├── build ├── build
│   └── lib │   └── lib
│   └── server23 │   └── server23
│   ├── __init__.py │   ├── __init__.py
│   └── server23.py │   └── server23.py
├── DEBIAN ├── DEBIAN
│   └── control │   └── control
├── install.sh ├── install.sh
├── setup.py ├── setup.py
└── src └── src
└── server23 └── server23
├── __init__.py ├── __init__.py
└── server23.py └── server23.py
* python setup.py install * python setup.py install
Installation is 2 step action. First step = build. Second step = final local installation. Installation is 2 step action. First step = build. Second step = final local installation.
tree: tree:
├── DEBIAN ├── DEBIAN
│   └── control │   └── control
├── build ├── build
│   └── lib │   └── lib
│   └── server23 │   └── server23
│   ├── __init__.py │   ├── __init__.py
│   └── server23.py │   └── server23.py
└── usr └── usr
├── bin ├── bin
│   └── server22 │   └── server22
├── lib ├── lib
│   └── python3 │   └── python3
│   └── dist-packages │   └── dist-packages
│   ├── server22 │   ├── server22
│   │   ├── __init__.py │   │   ├── __init__.py
│   │   └── server22.py │   │   └── server22.py
│   └── server22-2.2.2.egg-info │   └── server22-2.2.2.egg-info
│   ├── dependency_links.txt │   ├── dependency_links.txt
│   ├── entry_points.txt │   ├── entry_points.txt
│   ├── PKG-INFO │   ├── PKG-INFO
│   └── top_level.txt │   └── top_level.txt
└── share └── share
└── doc └── doc
└── server22 └── server22
├── copyright ├── copyright
└── changelog.gz └── changelog.gz
* python setup.py sdist * python setup.py sdist
It will create source distribution - and zip it, so you can ship it :) It will create source distribution - and zip it, so you can ship it :)
tree: tree:
├── DEBIAN ├── DEBIAN
│   └── control │   └── control
├── dist ├── dist
│   └── server24-2.2.2.tar.gz │   └── server24-2.2.2.tar.gz
├── install.sh ├── install.sh
├── m.md ├── m.md
├── setup.py ├── setup.py
└── src └── src
├── server24 ├── server24
│   ├── __init__.py │   ├── __init__.py
│   └── server24.py │   └── server24.py
└── server24.egg-info └── server24.egg-info
├── dependency_links.txt ├── dependency_links.txt
├── entry_points.txt ├── entry_points.txt
├── PKG-INFO ├── PKG-INFO
├── SOURCES.txt ├── SOURCES.txt
└── top_level.txt └── top_level.txt
* python setup.py develop * python setup.py develop
Executes build, installation but creates a simlink, so every changes made are immediately visible, without need of reinstall. Executes build, installation but creates a simlink, so every changes made are immediately visible, without need of reinstall.
@@ -210,204 +210,204 @@ NOTE: bdist_rpm & bdist_wininst does not work on Debian based distrubutions! You
## Structure of setup.py ## Structure of setup.py
- from PyPA (Python Packaging Authority), https://www.pypa.io/en/latest/ - from PyPA (Python Packaging Authority), https://www.pypa.io/en/latest/
"""A setuptools based setup module. """A setuptools based setup module.
See: See:
https://packaging.python.org/guides/distributing-packages-using-setuptools/ https://packaging.python.org/guides/distributing-packages-using-setuptools/
https://github.com/pypa/sampleproject https://github.com/pypa/sampleproject
""" """
- Always prefer setuptools over distutils - Always prefer setuptools over distutils
from setuptools import setup, find_packages from setuptools import setup, find_packages
import pathlib import pathlib
here = pathlib.Path(__file__).parent.resolve() here = pathlib.Path(__file__).parent.resolve()
- Get the long description from the README file - Get the long description from the README file
long_description = (here / 'README.md').read_text(encoding='utf-8') long_description = (here / 'README.md').read_text(encoding='utf-8')
- Arguments marked as "Required" below must be included for upload to PyPI. - Arguments marked as "Required" below must be included for upload to PyPI.
- Fields marked as "Optional" may be commented out. - Fields marked as "Optional" may be commented out.
setup( setup(
# This is the name of your project. The first time you publish this # 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 # package, this name will be registered for you. It will determine how
# users can install this project, e.g.: # users can install this project, e.g.:
# #
# $ pip install sampleproject # $ pip install sampleproject
# #
# And where it will live on PyPI: https://pypi.org/project/sampleproject/ # And where it will live on PyPI: https://pypi.org/project/sampleproject/
# #
# There are some restrictions on what makes a valid project name # There are some restrictions on what makes a valid project name
# specification here: # specification here:
# https://packaging.python.org/specifications/core-metadata/#name # https://packaging.python.org/specifications/core-metadata/#name
name='sampleproject', # Required name='sampleproject', # Required
# Versions should comply with PEP 440: # Versions should comply with PEP 440:
# https://www.python.org/dev/peps/pep-0440/ # https://www.python.org/dev/peps/pep-0440/
# #
# For a discussion on single-sourcing the version across setup.py and the # For a discussion on single-sourcing the version across setup.py and the
# project code, see # project code, see
# https://packaging.python.org/en/latest/single_source_version.html # https://packaging.python.org/en/latest/single_source_version.html
version='2.0.0', # Required version='2.0.0', # Required
# This is a one-line description or tagline of what your project does. This # This is a one-line description or tagline of what your project does. This
# corresponds to the "Summary" metadata field: # corresponds to the "Summary" metadata field:
# https://packaging.python.org/specifications/core-metadata/#summary # https://packaging.python.org/specifications/core-metadata/#summary
description='A sample Python project', # Optional description='A sample Python project', # Optional
# This is an optional longer description of your project that represents # This is an optional longer description of your project that represents
# the body of text which users will see when they visit PyPI. # 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 # 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) # that file directly (as we have already done above)
# #
# This field corresponds to the "Description" metadata field: # This field corresponds to the "Description" metadata field:
# https://packaging.python.org/specifications/core-metadata/#description-optional # https://packaging.python.org/specifications/core-metadata/#description-optional
long_description=long_description, # Optional long_description=long_description, # Optional
# Denotes that our long_description is in Markdown; valid values are # Denotes that our long_description is in Markdown; valid values are
# text/plain, text/x-rst, and text/markdown # text/plain, text/x-rst, and text/markdown
# #
# Optional if long_description is written in reStructuredText (rst) but # Optional if long_description is written in reStructuredText (rst) but
# required for plain-text or Markdown; if unspecified, "applications should # required for plain-text or Markdown; if unspecified, "applications should
# attempt to render [the long_description] as text/x-rst; charset=UTF-8 and # 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) # fall back to text/plain if it is not valid rst" (see link below)
# #
# This field corresponds to the "Description-Content-Type" metadata field: # This field corresponds to the "Description-Content-Type" metadata field:
# https://packaging.python.org/specifications/core-metadata/#description-content-type-optional # https://packaging.python.org/specifications/core-metadata/#description-content-type-optional
long_description_content_type='text/markdown', # Optional (see note above) long_description_content_type='text/markdown', # Optional (see note above)
# This should be a valid link to your project's main homepage. # This should be a valid link to your project's main homepage.
# #
# This field corresponds to the "Home-Page" metadata field: # This field corresponds to the "Home-Page" metadata field:
# https://packaging.python.org/specifications/core-metadata/#home-page-optional # https://packaging.python.org/specifications/core-metadata/#home-page-optional
url='https://github.com/pypa/sampleproject', # Optional url='https://github.com/pypa/sampleproject', # Optional
# This should be your name or the name of the organization which owns the # This should be your name or the name of the organization which owns the
# project. # project.
author='A. Random Developer', # Optional author='A. Random Developer', # Optional
# This should be a valid email address corresponding to the author listed # This should be a valid email address corresponding to the author listed
# above. # above.
author_email='author@example.com', # Optional author_email='author@example.com', # Optional
# Classifiers help users find your project by categorizing it. # Classifiers help users find your project by categorizing it.
# #
# For a list of valid classifiers, see https://pypi.org/classifiers/ # For a list of valid classifiers, see https://pypi.org/classifiers/
classifiers=[ # Optional classifiers=[ # Optional
# How mature is this project? Common values are # How mature is this project? Common values are
# 3 - Alpha # 3 - Alpha
# 4 - Beta # 4 - Beta
# 5 - Production/Stable # 5 - Production/Stable
'Development Status :: 3 - Alpha', 'Development Status :: 3 - Alpha',
# Indicate who your project is intended for # Indicate who your project is intended for
'Intended Audience :: Developers', 'Intended Audience :: Developers',
'Topic :: Software Development :: Build Tools', 'Topic :: Software Development :: Build Tools',
# Pick your license as you wish # Pick your license as you wish
'License :: OSI Approved :: MIT License', 'License :: OSI Approved :: MIT License',
# Specify the Python versions you support here. In particular, ensure # Specify the Python versions you support here. In particular, ensure
# that you indicate you support Python 3. These classifiers are *not* # that you indicate you support Python 3. These classifiers are *not*
# checked by 'pip install'. See instead 'python_requires' below. # checked by 'pip install'. See instead 'python_requires' below.
'Programming Language :: Python :: 3', 'Programming Language :: Python :: 3',
'Programming Language :: Python :: 3.6', 'Programming Language :: Python :: 3.6',
'Programming Language :: Python :: 3.7', 'Programming Language :: Python :: 3.7',
'Programming Language :: Python :: 3.8', 'Programming Language :: Python :: 3.8',
'Programming Language :: Python :: 3.9', 'Programming Language :: Python :: 3.9',
'Programming Language :: Python :: 3 :: Only', 'Programming Language :: Python :: 3 :: Only',
],
# 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 list of additional keywords, separated
# by commas, to be used to assist searching for the distribution in a
# larger catalog.
keywords='sample, setuptools, development', # Optional
# When your source code is in a subdirectory under the project root, e.g.
# `src/`, it is necessary to specify the `package_dir` argument.
package_dir={'': 'src'}, # 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(where='src'), # Required
# 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. See
# https://packaging.python.org/guides/distributing-packages-using-setuptools/#python-requires
python_requires='>=3.6, <4',
# 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=['peppercorn'], # 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.
package_data={ # Optional
'sample': ['package_data.dat'],
},
# 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/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': [
'sample=sample:main',
], ],
},
# List additional URLs that are relevant to your project as a dict. # This field adds keywords for your project which will appear on the
# # project page. What does your project relate to?
# This field corresponds to the "Project-URL" metadata fields: #
# https://packaging.python.org/specifications/core-metadata/#project-url-multiple-use # Note that this is a list of additional keywords, separated
# # by commas, to be used to assist searching for the distribution in a
# Examples listed include a pattern for specifying where the package tracks # larger catalog.
# issues, where the source is hosted, where to say thanks to the package keywords='sample, setuptools, development', # Optional
# maintainers, and where to support the project financially. The key is
# what's used to render the link text on PyPI. # When your source code is in a subdirectory under the project root, e.g.
project_urls={ # Optional # `src/`, it is necessary to specify the `package_dir` argument.
'Bug Reports': 'https://github.com/pypa/sampleproject/issues', package_dir={'': 'src'}, # Optional
'Funding': 'https://donate.pypi.org',
'Say Thanks!': 'http://saythanks.io/to/example', # You can just specify package directories manually here if your project is
'Source': 'https://github.com/pypa/sampleproject/', # 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(where='src'), # Required
# 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. See
# https://packaging.python.org/guides/distributing-packages-using-setuptools/#python-requires
python_requires='>=3.6, <4',
# 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=['peppercorn'], # 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.
package_data={ # Optional
'sample': ['package_data.dat'],
},
# 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/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': [
'sample=sample: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/pypa/sampleproject/issues',
'Funding': 'https://donate.pypi.org',
'Say Thanks!': 'http://saythanks.io/to/example',
'Source': 'https://github.com/pypa/sampleproject/',
},
)