Martin v. Löwis wrote:
>> One thing I'd like to see in the list are real names of committers,
>> not tracker names. Of course, people looking for people to assign a bug
>> to should not have to search for the tracker name, so I'd like to make
>> another request (that Brett already made when we swi
> One thing I'd like to see in the list are real names of committers,
> not tracker names. Of course, people looking for people to assign a bug
> to should not have to search for the tracker name, so I'd like to make
> another request (that Brett already made when we switched trackers):
>
> Cou
Fred Drake wrote:
> On Thu, Sep 17, 2009 at 10:38, Georg Brandl wrote:
>> So the plan would be to consolidate these into another set of rst docs,
>> having them in the repo, editable by every committer, as well as
>> published
>> somewhere on python.org (devdocs.python.org or somesuch).
>
> On Se
On Thu, Sep 17, 2009 at 7:26 PM, A.M. Kuchling wrote:
> On Thu, Sep 17, 2009 at 11:32:25PM +0200, Georg Brandl wrote:
>> > Should we do something similar with the FAQs at
>> > http://www.python.org/doc/faq/ ?
>>
>> They would then go into the main docs, I guess?
>
> That would make sense. However
On Thu, 17 Sep 2009 at 14:19, Fred Drake wrote:
One of the reasons www.python.org/doc/ was considered less discoverable was
the about of only-sometimes-interesting information there; docs.python.org
contains only "current" docs (for some vague notion of current and only,
given that dev builds a
On Thu, Sep 17, 2009 at 11:32:25PM +0200, Georg Brandl wrote:
> > Should we do something similar with the FAQs at
> > http://www.python.org/doc/faq/ ?
>
> They would then go into the main docs, I guess?
That would make sense. However, we already have seven different FAQs
there, so I don't think
Paul Moore wrote:
> runpy - Nick Coghlan
And for the general interest table, the import system and the AST
compiler are the two main areas that I know better than most.
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
-
A.M. Kuchling schrieb:
> On Thu, Sep 17, 2009 at 07:38:50PM +0200, Georg Brandl wrote:
>> So the plan would be to consolidate these into another set of rst docs,
>> having them in the repo, editable by every committer, as well as published
>> somewhere on python.org (devdocs.python.org or somesuch)
On Sep 17, 2009, at 10:59 AM, Brett Cannon wrote:
On Thu, Sep 17, 2009 at 10:38, Georg Brandl wrote:
R. David Murray schrieb:
I floated a proposal on stdlib-sig to create a file named
Misc/maintainers.rst. The purpose of this file is to collect
knowledge
about who knows which modules well
On Thu, Sep 17, 2009 at 1:38 PM, Georg Brandl wrote:
> R. David Murray schrieb:
>> I floated a proposal on stdlib-sig to create a file named
>> Misc/maintainers.rst. The purpose of this file is to collect knowledge
>> about who knows which modules well enough to make decision about issues
>> in t
On Thu, Sep 17, 2009 at 10:38, Georg Brandl wrote:
So the plan would be to consolidate these into another set of rst
docs,
having them in the repo, editable by every committer, as well as
published
somewhere on python.org (devdocs.python.org or somesuch).
On Sep 17, 2009, at 1:56 PM, Brett
2009/9/17 R. David Murray :
> Feel free to respond with comments about the header text, but more
> importantly let me know what you know about who (especially if it is you)
> should be listed for each module, platform, and topic, and feel free to
> suggest additional topics. My goal is to record t
On Thu, Sep 17, 2009 at 07:38:50PM +0200, Georg Brandl wrote:
> So the plan would be to consolidate these into another set of rst docs,
> having them in the repo, editable by every committer, as well as published
> somewhere on python.org (devdocs.python.org or somesuch).
+1.
Should we do somethi
R. David Murray wrote:
On Thu, 17 Sep 2009 at 10:57, Brett Cannon wrote:
Looks great to me! Only thing missing that I can think of is sticking
Eric down as the guy who does str.format(). =)
OK, I've added that one to the last table ;)
Awesome! I get to spend even more time on formatting stri
On Thu, 17 Sep 2009 at 14:08, R. David Murray wrote:
On Thu, 17 Sep 2009 at 10:59, Brett Cannon wrote:
On Thu, Sep 17, 2009 at 10:38, Georg Brandl wrote:
> ??Could we *please* have tracker names that match the committer names?
>
> (This doesn't even need to be done by the individual users,
On Thu, 17 Sep 2009 at 10:57, Brett Cannon wrote:
Looks great to me! Only thing missing that I can think of is sticking
Eric down as the guy who does str.format(). =)
OK, I've added that one to the last table ;)
--David
___
Python-Dev mailing list
Py
On Thu, 17 Sep 2009 at 10:59, Brett Cannon wrote:
On Thu, Sep 17, 2009 at 10:38, Georg Brandl wrote:
??Could we *please* have tracker names that match the committer names?
(This doesn't even need to be done by the individual users, I would
volunteer to rename all committer accounts and notify
On Thu, Sep 17, 2009 at 10:38, Georg Brandl wrote:
> R. David Murray schrieb:
>> I floated a proposal on stdlib-sig to create a file named
>> Misc/maintainers.rst. The purpose of this file is to collect knowledge
>> about who knows which modules well enough to make decision about issues
>> in the
Looks great to me! Only thing missing that I can think of is sticking
Eric down as the guy who does str.format(). =)
On Thu, Sep 17, 2009 at 10:14, R. David Murray wrote:
> I floated a proposal on stdlib-sig to create a file named
> Misc/maintainers.rst. The purpose of this file is to collect kn
On Thu, Sep 17, 2009 at 10:38, Georg Brandl wrote:
> R. David Murray schrieb:
>> I floated a proposal on stdlib-sig to create a file named
>> Misc/maintainers.rst. The purpose of this file is to collect knowledge
>> about who knows which modules well enough to make decision about issues
>> in the
R. David Murray schrieb:
> I floated a proposal on stdlib-sig to create a file named
> Misc/maintainers.rst. The purpose of this file is to collect knowledge
> about who knows which modules well enough to make decision about issues
> in the tracker when the participants in the issue aren't sure, a
I floated a proposal on stdlib-sig to create a file named
Misc/maintainers.rst. The purpose of this file is to collect knowledge
about who knows which modules well enough to make decision about issues
in the tracker when the participants in the issue aren't sure, and to
write down the community k
22 matches
Mail list logo
