Don't force users to use distribute

[GoogleCodeExporter]

You should not force users to use distribute in order to install the package 
since we may want to use setuptools, pip or pure distutils for various reasons. 
You'll find a patch attached that solves this specific issue.

Original issue reported on code.google.com by sylvain....@gmail.com on 3 May 2012 at 1:44

Attachments:

• RPi-setup.patch

[GoogleCodeExporter]

Have created a Raspbian .deb package and you can now:
sudo apt-get install python-rpi.gpio
sudo apt-get install python3-rpi.gpio

Setuptools is dead.  Distribute is it's replacement.
See http://guide.python-distribute.org/introduction.html#state-of-packaging-info

If a future change is made, then it will be to use pip.  For now, you'll just 
have to put up with it, or use apt-get as above.

Original comment by btcros...@googlemail.com on 9 Sep 2012 at 2:56

• Changed state: Fixed
• Added labels: Type-Other, Priority-Low
• Removed labels: Type-Defect, Priority-Medium

[GoogleCodeExporter]

I agree with you... in theory!

Now imagine I want to use another package that does just that, but with 
setuptools: I'm stuck. That's why it's not a good idea to force users to use a 
given packaging tool, even if it's state of the art.

However, that would be ok if you try to import setuptools and fallback to 
installing distribute if it's not available.

Original comment by sylvain....@gmail.com on 18 Dec 2012 at 8:21

[GoogleCodeExporter]

Another good reason here:
http://www.raspberrypi.org/phpBB3/viewtopic.php?t=22633&p=215218

Original comment by sylvain....@gmail.com on 18 Dec 2012 at 8:25

[GoogleCodeExporter]

And there:
http://lists.debian.org/debian-python/2012/01/msg00055.html

Original comment by sylvain....@gmail.com on 18 Dec 2012 at 8:27