On Tue, Apr 27, 2010 at 09:41:02AM +0200, Tarek Ziadé wrote:
> On Tue, Apr 27, 2010 at 1:24 AM, Toshio Kuratomi wrote:
> > On Mon, Apr 26, 2010 at 05:46:55PM -0400, Barry Warsaw wrote:
> >> On Apr 26, 2010, at 09:39 PM, Tarek Ziadé wrote:
> >>
> >> >You should be permissive on that one. Until we k
On Tue, Apr 27, 2010 at 2:43 AM, David Cournapeau wrote:
> On Tue, Apr 27, 2010 at 5:10 AM, Piotr Ożarowski wrote:
>
>> if there's no other way (--install-data is ignored right now, and I know
>> you're doing a great work to change that, thanks BTW), one could always
>> use it in *one* place and
On Tue, Apr 27, 2010 at 1:24 AM, Toshio Kuratomi wrote:
> On Mon, Apr 26, 2010 at 05:46:55PM -0400, 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 devel
On Tue, Apr 27, 2010 at 5:10 AM, Piotr Ożarowski wrote:
> if there's no other way (--install-data is ignored right now, and I know
> you're doing a great work to change that, thanks BTW), one could always
> use it in *one* place and later import the result in other parts of
> the code (instead of
On 27/04/2010 00:26, James Mills wrote:
On Tue, Apr 27, 2010 at 9:15 AM, David Malcolm wrote:
On Mon, 2010-04-26 at 21:19 +0200, Piotr Ożarowski wrote:
Many Python module developers do not want their work to be distributed
by Debian (and probably by other Linux distributions), here's
On Tue, Apr 27, 2010 at 9:15 AM, David Malcolm wrote:
> On Mon, 2010-04-26 at 21:19 +0200, Piotr Ożarowski wrote:
>> Many Python module developers do not want their work to be distributed
>> by Debian (and probably by other Linux distributions), here's a list of
> Thanks! Not just Debian: I can
On Mon, Apr 26, 2010 at 05:46:55PM -0400, 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..
>
On Mon, 2010-04-26 at 21:19 +0200, Piotr Ożarowski wrote:
> Hi,
>
> Many Python module developers do not want their work to be distributed
> by Debian (and probably by other Linux distributions), here's a list of
Thanks! Not just Debian: I can confirm, from bitter experience, that
your list is a
On Mon, Apr 26, 2010 at 11:56 PM, Robert Kern wrote:
[..]
>
> 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/ subdirec
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
On Apr 27, 2010, at 12:03 AM, Tarek Ziadé wrote:
>On Mon, Apr 26, 2010 at 11:45 PM, Barry Warsaw wrote:
>[..]
>>
>> For example, there's a nice tool called 'Quickly' that builds application
>> templates using best practices. It is opinionated, but designed for the
>> opportunistic programmer. I
On Mon, Apr 26, 2010 at 11: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
On Mon, Apr 26, 2010 at 11:45 PM, Barry Warsaw wrote:
[..]
>
> For example, there's a nice tool called 'Quickly' that builds application
> templates using best practices. It is opinionated, but designed for the
> opportunistic programmer. I've been thinking about writing a Python
> application a
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 pkg_resources t
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 pkg_resources the best practice for this? (I'm pretty s
On Apr 26, 2010, at 09:19 PM, Piotr Ożarowski wrote:
>Many Python module developers do not want their work to be distributed
>by Debian (and probably by other Linux distributions), here's a list of
>hints that will help you accomplish that goal:
Okay, it took me a few bullet items to realize you
On Mon, Apr 26, 2010 at 10:10 PM, Piotr Ożarowski wrote:
> [Tarek Ziadé, 2010-04-26]
>> Great hints, I'll try to follow them... and they could make a good
>> section in the Hitchhiker's guide to packaging ;)
>
> How about these two:
> http://us.pycon.org/media/2010/talkdata/PyCon2010/038/paper.htm
[Tarek Ziadé, 2010-04-26]
> Great hints, I'll try to follow them... and they could make a good
> section in the Hitchhiker's guide to packaging ;)
How about these two:
http://us.pycon.org/media/2010/talkdata/PyCon2010/038/paper.html
http://wiki.debian.org/GettingPackaged
> [...]
> > * ignore FHS
On Mon, Apr 26, 2010 at 9:19 PM, Piotr Ożarowski wrote:
> Hi,
>
> Many Python module developers do not want their work to be distributed
> by Debian (and probably by other Linux distributions), here's a list of
> hints that will help you accomplish that goal:
Great hints, I'll try to follow them.
Hi,
Many Python module developers do not want their work to be distributed
by Debian (and probably by other Linux distributions), here's a list of
hints that will help you accomplish that goal:
* depend on unstable or unreleased software (even if you
use it only to generate docs or do unit test
20 matches
Mail list logo
