It’s a good start. I went through the entire article today. I got a basic package uploaded. As I researched getting this working, there were a lot of IDE configuration issues and not exactly understanding how a package works when installed. A more complete example program would be useful. My feedback is: A package needs more files than this. From my research, there is more like this.

./LICENSE
./requirements.txt
./sample_program
./sample_program/sample_program.py
./sample_program/__init__.py
./sample_program/__version__.py
./Makefile
./tests
./tests/test_basic.py
./tests/context.py
./docs
./README.md
./setup.py
./__init__.py
./version.py

I am unsure how this all packages up for a single program. I see these files in different versions.

I have seen this construct in many programs. I am interested in how these variables are used within programs.

# Program Description Variables
__author__ = "xxxxx"
__copyright__ = "Copyright 2019, " + __author__
__credits__ = ["xxxxx"]
__license__ = "GPL3"
__version__ = "0.1.0"
__maintainer__ = "xx"xx
__status__ = "Alpha"
__created___ = "01/05/2020"
__updated___ = ""
__prog_name__ = os.path.basename(__file__)

Also how to package a python program so that it runs as a binary after install. I couldn’t quite get an understanding of how/why PyDev does packaging. Something to explain that would also be useful.

Reference Links:

Packaging Python Projects - Python Packaging User Guide