You can easily install a third-party package, which will bootstrap you to one way to create package. But, okay, you want to install a package you wrote, using

You can easily install a third-party package, which will bootstrap you to one way to create package. But, okay, you want to install a package you wrote, using only a stock Python installation. 1) Why? That is, you can modify your PYTHONPATH to include your working directory. 2) Why use an installer? For simple packages you can drop the file/directory into site-packages. 3) I've been using Python for long enough that I distributed Python packages before there was a setup.py or setuptools. I used a Makefile. In fact, I still use a Makefile when I need faster build cycle times as setup.py does not do good dependency management. 4) I showed you how to build a wheel using only stock Python code, which lets you use pip as the installer. Finally, with a source distribution you can tweak Python's own Makefile to build your own module, including a C extension: https://docs.python.org/3/extending/extending.html#compilation-and-linkage https://docs.python.org/3/extending/extending.html#compilati... Why don't any of these resolve your issue?