Windows
py -m pip install --upgrade pip
Linux/MAC OS
python3 -m pip install --upgrade pip
packaging_tutorial/
├── LICENSE
├── pyproject.toml
├── README.md
├── setup.cfg
├── src/
│ └── example_package/
│ ├── __init__.py
│ └── example.py
└── tests/
touch LICENSE
touch pyproject.toml
touch setup.cfg
mkdir src/mypackage
touch src/mypackage/__init__.py
touch src/mypackage/main.py
mkdir tests
This file tells tools like pip and build how to create your project
[build-system]
requires = [
"setuptools>=42",
"wheel"
]
build-backend = "setuptools.build_meta"
build-system.requires gives a list of packages that are needed to build your package. Listing something here will only make it available during the build, not after it is installed.
build-system.build-backend is the name of Python object that will be used to perform the build. If you were to use a different build system, such as flit or poetry, those would go here, and the configuration details would be completely different than the setuptools configuration described below.
Using setup.cfg is a best practice, but you could have a dynamic setup file using setup.py
[metadata]
name = xyShiftSplit
version = 0.0.1
author = Rifqi khairurrahman
author_email = eaglemaster7@gmail.com
description = this package to make easy to create X and Y data, shift and split from same dataset
long_description = file: README.md
long_description_content_type = text/markdown
url = https://github.com/pypa/sampleproject
project_urls =
Bug Tracker = https://github.com/pypa/sampleproject/issues
classifiers =
Programming Language :: Python :: 3
License :: OSI Approved :: MIT License
Operating System :: OS Independent
[options]
package_dir =
= src
packages = find:
python_requires = >=3.6
[options.packages.find]
where = src
Windows
py -m pip install --upgrade build
Linux/MAC OS
python3 -m pip install --upgrade build
py -m build
python.exe -m twine upload dist/*