Hey
I was reading this :
http://distlib.readthedocs.org/en/latest/overview.html#what-was-the-problem-with-packaging
and I thought I should bring up that distutils2 has implemented a way to
define data files that can be installed in the right places on the
target system. right here being
Tarek Ziadé tarek at ziade.org writes:
and I thought I should bring up that distutils2 has implemented a way to
define data files that can be installed in the right places on the
target system. right here being what the linux distros decides, or the
default win location etc.
There is a
On 11/18/12 10:15 PM, Vinay Sajip wrote:
Tarek Ziadé tarek at ziade.org writes:
and I thought I should bring up that distutils2 has implemented a way to
define data files that can be installed in the right places on the
target system. right here being what the linux distros decides, or the
Tarek Ziadé tarek at ziade.org writes:
Having a indirection like distutils2's resources allows the data files
to live alongside the code
in development and to be installed wherever that's desired by the
distro, without breaking
the code as long as it uses the indirection function to find
On 11/18/2012 05:08 PM, Vinay Sajip wrote:
Tarek Ziadé tarek at ziade.org writes:
Having a indirection like distutils2's resources allows the data files
to live alongside the code
in development and to be installed wherever that's desired by the
distro, without breaking
the code as long as it
Just come to my mind data test related to a package would be a natural
candidate:
mypack
|- __init__.py
|- test
|- __init__.py
|- test0.py
|- data
|- data.for.test0.dat
It is natural deploying them as part of an installer file.
I don't see why
On 11/18/12 11:15 PM, Chris McDonough wrote:
On 11/18/2012 05:08 PM, Vinay Sajip wrote:
Tarek Ziadé tarek at ziade.org writes:
Having a indirection like distutils2's resources allows the data files
to live alongside the code
in development and to be installed wherever that's desired by the
On 11/18/12 11:25 PM, Antonio Cavallo wrote:
Just come to my mind data test related to a package would be a natural
candidate:
mypack
|- __init__.py
|- test
|- __init__.py
|- test0.py
|- data
|- data.for.test0.dat
It is natural deploying them
On 11/18/2012 05:33 PM, Tarek Ziadé wrote:
On 11/18/12 11:15 PM, Chris McDonough wrote:
On 11/18/2012 05:08 PM, Vinay Sajip wrote:
Tarek Ziadé tarek at ziade.org writes:
Having a indirection like distutils2's resources allows the data files
to live alongside the code
in development and to be
On 11/18/12 11:45 PM, Chris McDonough wrote:
I don't really take exception to having such a feature (although I
would be unlikely to use it), but I do take exception to the first
paragraph of the description you pointed at:
This section describes the files used by the project which must not
On 11/18/2012 05:55 PM, Tarek Ziadé wrote:
On 11/18/12 11:45 PM, Chris McDonough wrote:
I don't really take exception to having such a feature (although I
would be unlikely to use it), but I do take exception to the first
paragraph of the description you pointed at:
This section describes the
11 matches
Mail list logo
