[Python-Dev] what to do if you don't want your module in Debian (original) (raw)

Barry Warsaw barry at python.org
Tue Apr 27 00:21:10 CEST 2010

On Apr 26, 2010, at 04:56 PM, Robert Kern wrote:

On 4/26/10 4:46 PM, Barry Warsaw wrote:

On Apr 26, 2010, at 09:39 PM, Tarek Ziadé wrote:

You should be permissive on that one. Until we know how to describe resource files properly, file is what developer use when they need their projects to be portable.. Until then, isn't pkgresources the best practice for this? (I'm pretty sure we've talked about this before.) I don't think the OP is really speaking against using file per se, but rather putting data into the package however it is accessed. The Linux-packager preferred practice is to install into the appropriate /usr/shared/ subdirectory. Writing portable libraries (with portable setup.py files!) is difficult to do that way, though.

Tarek pointed to the rest page that captured some of the thinking on this developed at Pycon. There's really two sides to it - what does the programmer write and how does that integrate with the system? I really don't think the developer should go through any contortions to make it work right for the platform. For one thing, there's no way they can do it for every platform their code might end up on. It's a lose to attempt it. Tarek's design allows for separation of concerns and indirection so the programmer can worry about the parts they care about, and the platform packagers can worry about the parts they care about.

-Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: <http://mail.python.org/pipermail/python-dev/attachments/20100426/53888f80/attachment.pgp>

More information about the Python-Dev mailing list