On Thu, Apr 19, 2012 at 11:35 AM, Stephen J. Turnbull
wrote:
> On Thu, Apr 19, 2012 at 5:16 AM, Ned Deily wrote:
>
>>> Ethan Furman wrote:
>
>>> > How does one follow the bug tracker?
>
> [informative and useful answers elided]
>
> I would like to summarize this thread and add it to the dev
> do
On Thu, Apr 19, 2012 at 5:16 AM, Ned Deily wrote:
>> Ethan Furman wrote:
>> > How does one follow the bug tracker?
[informative and useful answers elided]
I would like to summarize this thread and add it to the dev
documentation. Where should it go? (If nobody bothers to answer,
I'll assume
In article <20120418211404.2700d...@pitrou.net>,
Antoine Pitrou wrote:
> On Wed, 18 Apr 2012 12:19:39 -0700
> Ethan Furman wrote:
> > Brian Curtin wrote:
> > > On Wed, Apr 18, 2012 at 13:07, Ethan Furman wrote:
> > > Those who follow the bug tracker will see the issue and act
> > > accordingly.
On 4/18/2012 3:19 PM, Ethan Furman wrote:
Brian Curtin wrote:
On Wed, Apr 18, 2012 at 13:07, Ethan Furman wrote:
Those who follow the bug tracker will see the issue and act
accordingly.
How does one follow the bug tracker?
I look at the Friday summary, paying particular attention to issues
Brian Curtin wrote:
On Wed, Apr 18, 2012 at 13:07, Ethan Furman wrote:
http://bugs.python.org/issue14617
Patch attached to issue.
Can I request that you not immediately post issues to python-dev?
Those who follow the bug tracker will see the issue and act
accordingly.
(unless I missed some
Am 18.04.2012 21:19, schrieb Ethan Furman:
> Brian Curtin wrote:
>> On Wed, Apr 18, 2012 at 13:07, Ethan Furman wrote:
>> Those who follow the bug tracker will see the issue and act
>> accordingly.
>
> How does one follow the bug tracker?
I do by subscribing to new-bugs-announce.
Regards,
Marti
On Wed, 18 Apr 2012 12:19:39 -0700
Ethan Furman wrote:
> Brian Curtin wrote:
> > On Wed, Apr 18, 2012 at 13:07, Ethan Furman wrote:
> > Those who follow the bug tracker will see the issue and act
> > accordingly.
>
> How does one follow the bug tracker?
Checking it frequently is a possibility.
2012/4/18 Ethan Furman :
> Brian Curtin wrote:
>>
>> On Wed, Apr 18, 2012 at 13:07, Ethan Furman wrote:
>> Those who follow the bug tracker will see the issue and act
>> accordingly.
>
>
> How does one follow the bug tracker?
One checks occasionally to see if anything interesting has popped up
or
Brian Curtin wrote:
On Wed, Apr 18, 2012 at 13:07, Ethan Furman wrote:
Those who follow the bug tracker will see the issue and act
accordingly.
How does one follow the bug tracker?
~Ethan~
___
Python-Dev mailing list
Python-Dev@python.org
http://mai
On Wed, Apr 18, 2012 at 13:07, Ethan Furman wrote:
> http://bugs.python.org/issue14617
>
> Patch attached to issue.
Can I request that you not immediately post issues to python-dev?
Those who follow the bug tracker will see the issue and act
accordingly.
(unless I missed some explicit request th
http://bugs.python.org/issue14617
Patch attached to issue.
~Ethan~
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archi
11 matches
Mail list logo