build-process request: usage of python-setuptools. #875

New Issue

2016-07-06T19:15:30+02:00

ghost commented

2016-07-06 19:15:30 +02:00

(Migrated from github.com)

As I messaged @PeterSurda some time ago and provided a starting point for a setup.py,
using python-setuptools would help/benefit most if not all package maintainers who currently work around your in-repo provided methods.

I don't want you to put PyBitmessage on pypi, but I'd rather like to make most maintainers work easier. It can use setuptools without being on pypi.
From the technical side this might be considered not much of a priority, but I addressed this before the 0.6 release and nothing happened so far.

This is a non-trivial fix, but it would help the distribution of PyBitmessage and make maintainers happy with less lines of code to work around issues.
I have had an almost working setup.py, but I do not like to commit half finished work.
If Peter does not include it, I can search for it again, upload it to a public place and someone else with more insight on python-setuptools and PyBitmessage can fix it up.

As I messaged @PeterSurda some time ago and provided a starting point for a setup.py, using python-setuptools would help/benefit most if not all package maintainers who currently work around your in-repo provided methods. I don't want you to put PyBitmessage on pypi, but I'd rather like to make most maintainers work easier. It can use setuptools without being on pypi. From the technical side this might be considered not much of a priority, but I addressed this before the 0.6 release and nothing happened so far. This is a non-trivial fix, but it would help the distribution of PyBitmessage and make maintainers happy with less lines of code to work around issues. I have had an almost working setup.py, but I do not like to commit half finished work. If Peter does not include it, I can search for it again, upload it to a public place and someone else with more insight on python-setuptools and PyBitmessage can fix it up.

ghost commented

2016-07-16 13:15:18 +02:00

(Migrated from github.com)

This is related to #883 - bitmessagehash can keep its Makefile, best would be as asked in #886 to have it (btmsghash) moved to an external source.