View Full Version : Why are Python programs usually put in "Source Packages" rather than "Binary"

May 25th, 2009, 02:22 AM
According to the Debian Docs (http://www.debian.org/doc/manuals/maint-guide/ch-start.en.html#s-otherinfo): "There are two types of packages you can make, source and binary."

From what I've read, when people make a deb package for a Python program (or Ruby, or Perl, etc...), they usually make a "source package". Why is this? I can think of arguments for why a "binary package" could be a good fit as well. Actually, Python programs don't really fit terribly well into the source/binary dichotomy. Any thoughts?