4 ms·
Yes, but python packages are not for distributing that kind of software. You create a RPM _from_ a Python package. The RPM (and associated software) writes ini
by orf 6y ago
Yes, but python packages are not for distributing that kind of software.
You create a RPM _from_ a Python package. The RPM (and associated software) writes init files to the correct place. This bears no relevance on wheels, which absolutely should not be filled with district-specific knowledge about init scripts and should definitely not write to random hard-coded paths.
- u801e 6y ago> Yes, but python packages are not for distributing that kind of software. Where is that documented? The fact that setuptools and distutils.core supported building RPM packages from a setup.py file indicates that python intended to support application distribution. Why remove that capability when moving to wheels? > This bears no relevance on wheels, which absolutely should not be filled with district-specific knowledge about init scripts and should definitely not write to random hard-coded paths. One thing I noted while figuring out this issue is that running: pip install git+ssh://git@github.com/org/project.git@1.2.3 versus pip install project==1.2.3 where project was packaged as a wheel on pypi had different results with regards to where files referenced by the data_files named parameter in the setup call were placed on the file system. Given that, was the change intentional, or is it a bug with how wheels handle package installation?