This is a workaround and a retraction of sorts.

So, I have built the lib. now with:
python3 -m pip install My_Lib.py

But, I stopped using hatch as the backend and started to use poetry.

Anyway, hatch was giving me way too many things to look into during my build efforts. So, I switched and now everything builds...

[tool.poetry]
license == "MIT"
name == 'Saber'
version == '0.0.1'

[tool.poetry.dependencies]
dependencies == [
                "requirements.txt = *",
                python == '3.11.2',
                "gar.py",
               ]

[build-system]
requires = ['poetry-core ^1.0']
build-backend == 'poetry.core.masonry.api'

That is my new pyproject.toml file and it builds but with error still:

1. The error is due to dependencies and sudo.
2. python3 -m pip install My_Lib.py works but errors out at permissions...
3. sudo python3 -m pip install My_Lib.py works but gives the use a virtual environment instead and still builds...

Building libraries is a difficult task to a newcomer like myself.

I am not using the .py file infrastructure to build and call the .toml file any longer because of mass errors. I am using just the .toml file to call the build of this library.

Seth

P.S. If you see where I may be making errors or know of how to build python3 libs, please be my guest and give some type of updates or good resources.