My take on installing entry_points.txt is to add a {dist-info}
category in [files] resources = to copy extra files into the
.dist-info dir...
How do I write entry_points.txt when it is given as an argument to
setup(entry_points=...)? Should I write a build command hook to write
the file and a setu
On 05/16/2012 02:35 AM, Tarek Ziadé wrote:
1/ your argument about people being baffled about which tool to use will be worse if we
work outside the stdlib. Having packaging in the stdlib and distutils frozen here, leads
the path: "hey, the next tool in the stdlib is packaging"
It all depends
On 05/16/2012 02:55 AM, Tarek Ziadé wrote:
On 5/16/12 3:58 AM, Chris McDonough wrote:
Adding two more (packaging and distutils2) which are similarly
semi-documented and which don't even solve the problems that the
previous ones do would serve no purpose, and baking them into Python
itself will m
On 05/16/2012 02:35 AM, Tarek Ziadé wrote:
I know the idea of having packaging in the stdlib is something some
people disliked, from day 1. And if I recall correctly, you did not like
this either back then.
I've always been pro-stdlib-contains-a-package-installer-and-machinery,
and I still am.
On Wed, May 16, 2012 at 9:26 AM, Tarek Ziadé wrote:
> On 5/16/12 3:19 PM, Jim Fulton wrote:
>>
>> On Wed, May 16, 2012 at 2:55 AM, Tarek Ziadé wrote:
>>>
>>> On 5/16/12 3:58 AM, Chris McDonough wrote:
Adding two more (packaging and distutils2) which are similarly
semi-documented an
On 5/16/12 3:19 PM, Jim Fulton wrote:
On Wed, May 16, 2012 at 2:55 AM, Tarek Ziadé wrote:
On 5/16/12 3:58 AM, Chris McDonough wrote:
Adding two more (packaging and distutils2) which are similarly
semi-documented and which don't even solve the problems that the previous
ones do would serve no p
On Wed, May 16, 2012 at 2:55 AM, Tarek Ziadé wrote:
> On 5/16/12 3:58 AM, Chris McDonough wrote:
>>
>> Adding two more (packaging and distutils2) which are similarly
>> semi-documented and which don't even solve the problems that the previous
>> ones do would serve no purpose, and baking them into
Taking off Guido, I don't think he needs to be in the whole thread
On 5/16/12 10:30 AM, Paul Moore wrote:
I'm happy to summarise this on there. Let me know a link to the wiki
page.
I created http://wiki.python.org/moin/Packaging/Roadmap
But 2 points:
1. Binary distributions is *not* a Wind
On 16 May 2012 08:49, Tarek Ziadé wrote:
> On 5/16/12 9:40 AM, Paul Moore wrote:
>> This would be a very good step - but rather than simply getting
>> responses in the mailing list, can I suggest that we need some sort of
>> central location where the features still outstanding for packaging
>> ca
On 5/16/12 9:40 AM, Paul Moore wrote:
On 16 May 2012 07:55, Tarek Ziadé wrote:
I'd suggest you list what you can't do with "packaging" today and we work
through that list to point which features are missing and should be
developed *outside* the standard lib, and which ones are in "packaging" o
On 16 May 2012 07:55, Tarek Ziadé wrote:
> I'd suggest you list what you can't do with "packaging" today and we work
> through that list to point which features are missing and should be
> developed *outside* the standard lib, and which ones are in "packaging" or
> should be
This would be a very
I think the biggest thing missing wrt to command hooks is the ability
to have the tool automatically generate a OS specific wrapper (.exe for
windows, extension less with a shebang for *NIX). While I think it would
be useful for this feature to live in std lib, I don't think it's near as
require
12 matches
Mail list logo
