Closed MichalChromcak closed 3 years ago
@xhochy seeing your extensive professional background, would you know how this could be resolved? Thanks @cdeil for pointing me out to Uwe.
As this is setup with pyscaffold
, I'm unable to help sadly. pyscaffold
hides too many notches to understand easily what is going wrong.
@xhochy - Is there some project scaffold that you recommend for small pure-Python projects like this one?
In the past I've just written a minimal setup.py and setup.cfg manually, and used setuptools-scm for versioning, i.e. no scaffold project template really.
@therhaag any idea how to solve it?
@xhochy - Is there some project scaffold that you recommend for small pure-Python projects like this one?
I still have to opensource my scaffold but https://github.com/xhochy/fletcher/blob/master/setup.py is pretty close to it. In some cases, it helps to have a src/
directory where your main module(s) live. The important thing is that nowadays setuptools
and setuptools_scm
work with so small overhead that I believe that pyscaffold
is harming more than it helps as it obfuscates things a bit.
@MichalChromcak - my recommendation is to remove pyscaffold
and to use setuptools_scm
for versioning.
Personally I don't like the src
folder, but whether you put hcrystalball
directly or in src/hcrystalball
as-is, either way it'll work and be fine.
No plan big need to improve here
For some reason, the following section is not taken into account when creating distribution for PyPI with
python setup.py sdist bdist_wheel
.Such command creates
hcrystalball-0.1.4.post0.dev13+gfcf6b6d.dirty-py2.py3-none-any.whl
while support for Python 2 should not be included (python_requires = >=3.7
)Also dev and test folders are included in the tar.gz even they are mentioned in
[options.packages.find] exclude
https://github.com/heidelbergcement/hcrystalball/blob/1b42c12487c577b27034a2740e2c41a268e289bc/setup.cfg#L49-L54