Having a lot of meaningless options doesn't make meta data any more clear.
Well, they are not meaningless, but their role is fully fulfilled by other
options (Author and Maintainer fields in this particular case).
The use case for the Author field is that if Author wants to be contacted,
(s)he lea
The PEP 426 meta-data format allows only single Author and single
Maintainer per package, which is very inadequate to the way most popular
packages are developed.
The format should contains recommendation how to handle credits and process
them.
With the proper implementation the packaging format
Marcus Smith gmail.com> writes:
>
>
> Hello Vinay:
> I would say get it up to date, and then submit a pull.
> We can discuss details in the pull and see the travis results.
> It doesn't have to be final or an immediate merge candidate to submit a
pull for discussion.
Done. There are four fail
> fyi, there is dev list now for the "pypa" family of projects (most
> notably pip and virtualenv)
> "
> "pypa-dev" https://groups.google.com/forum/?fromgroups#!forum/pypa-dev
>
> This is *not* meant to replace distutils-sig.
>
> It's for more "day-to-day" discussions related to maintaining and
On Wed, Apr 24, 2013 at 11:19 AM, anatoly techtonik wrote:
> Having a lot of meaningless options doesn't make meta data any more clear.
> Well, they are not meaningless, but their role is fully fulfilled by other
> options (Author and Maintainer fields in this particular case).
>
> The use case fo
On Wed, Apr 24, 2013 at 5:06 PM, Lennart Regebro wrote:
> On Wed, Apr 24, 2013 at 11:19 AM, anatoly techtonik
> wrote:
> > Having a lot of meaningless options doesn't make meta data any more
> clear.
> > Well, they are not meaningless, but their role is fully fulfilled by
> other
> > options (Au
Keep in mind that this is the structured index metadata, which is only
used to grab requirements (for end users, who usually don't need the
other information at all) and used to generate cheese shop web pages.
AUTHORS.txt works when you don't need an automatic "email the author"
button. Or the proj
Hi everybody,
because there is no central place to look at and probably not all decisions
can be found in written form (like the abandoning of the fellow ship list,
when and why Tarek Ziadé decided to work on other things then
distribute/distutils2 and so on) I thought about writing a short summar
On Thu, Apr 25, 2013 at 12:45 AM, Daniel Holth wrote:
> Keep in mind that this is the structured index metadata, which is only
> used to grab requirements (for end users, who usually don't need the
> other information at all) and used to generate cheese shop web pages.
> AUTHORS.txt works when you
Erik:
Thanks for posting this.
fyi, the "Hitchhikers Guide to Packaging" was recently forked to this:
https://bitbucket.org/pypa/python-packaging-user-guide
This is a pypa project, and and aims to be somewhat authoritative.
It's currently too far out of date to be a good base for meaningful pull
re
On Thu, Apr 25, 2013 at 1:31 AM, Nick Coghlan wrote:
> Once the user guide and meta guide are in a better state, we'll update
> the stdlib distutils docs with a reference to them as a guide to a
> more up to date packaging toolchain.
Oops, I meant to echo Marcus' sentiment that additional hands i
Thanks for posting this Erik.
That's not a bad summary, and
http://www.scotttorborg.com/python-packaging/index.html looks like an
excellent resource.
We're currently trying to bring some order to the chaos, as described
at
http://python-notes.boredomandlaziness.org/en/latest/pep_ideas/core_packa
On Apr 24, 2013, at 11:14 AM, Nick Coghlan wrote:
> On Thu, Apr 25, 2013 at 12:45 AM, Daniel Holth wrote:
>> Keep in mind that this is the structured index metadata, which is only
>> used to grab requirements (for end users, who usually don't need the
>> other information at all) and used to ge
On Apr 24, 2013, at 12:42 PM, Donald Stufft wrote:
>
> On Apr 24, 2013, at 11:14 AM, Nick Coghlan wrote:
>
>> On Thu, Apr 25, 2013 at 12:45 AM, Daniel Holth wrote:
>>> Keep in mind that this is the structured index metadata, which is only
>>> used to grab requirements (for end users, who usu
Erik Bernoth gmail.com> writes:
> As a side note I like many sections in the distlib documentation [7].
Thanks for this feedback. Since distlib is under active development the
API reference section lags behind, but I've tried to keep the overview and
tutorial sections updated. If you have any sp
> * new (very incomplete) packaging guide for users
> * new (very incomplete) "working on packaging tools" meta-guide for
> contributors
>
Nick, btw, as I've started worked to work on these locally, I'm inclined to
just have one document (the "user guide") that handles both goals.
Why?
1) It's
not sure about gmane naming, but my first reaction w/o knowing much would
be like this:
pip/virtualenv user list
http://groups.google.com/group/python-virtualenv ->
gmane.comp.python.virtualenv
pypa-dev list
http://groups.google.com/group/pypa-dev -> gmane.comp.python.pypa.dev
as for whether
> not sure about gmane naming, but my first reaction w/o knowing much
> would be like this:
>
> pip/virtualenv user list
> http://groups.google.com/group/python-virtualenv ->
> gmane.comp.python.virtualenv
>
> pypa-dev list http://groups.google.com/group/pypa-dev ->
> gmane.comp.python.pypa.d
On 25 Apr 2013 05:38, "Marcus Smith" wrote:
>
>
>> * new (very incomplete) packaging guide for users
>> * new (very incomplete) "working on packaging tools" meta-guide for
>> contributors
>
>
> Nick, btw, as I've started worked to work on these locally, I'm inclined
to just have one document (
On Wed, Apr 24, 2013 at 7:54 PM, Donald Stufft wrote:
>
> On Apr 24, 2013, at 12:42 PM, Donald Stufft wrote:
>
> >
> > On Apr 24, 2013, at 11:14 AM, Nick Coghlan wrote:
> >
> >> On Thu, Apr 25, 2013 at 12:45 AM, Daniel Holth
> wrote:
> >>> Keep in mind that this is the structured index metadat
On Wed, Apr 24, 2013 at 6:14 PM, Nick Coghlan wrote:
> On Thu, Apr 25, 2013 at 12:45 AM, Daniel Holth wrote:
> > Keep in mind that this is the structured index metadata, which is only
> > used to grab requirements (for end users, who usually don't need the
> > other information at all) and used
On Apr 24, 2013, at 11:35 PM, anatoly techtonik wrote:
> To reach the consensus in this discussion, I guess we all agree that roles in
> software projects may differ greatly. Even the 4 user stories listed are not
> enough to give proper credits to all people involved. I guess we can reach
>
22 matches
Mail list logo
