Hi All,
Sorry if this is considered slightly off topic, but Sphinx is the tool
we use for the Python core docs so:
Who's looking after Sphinx nowadays? I've hit what I consider to be a bug:
https://groups.google.com/group/sphinx-dev/browse_thread/thread/197fc26ba570913d?hl=en
So I forked on
>> I have a few questions about feature freeze:
>>
>> (1) Is increasing test coverage acceptable during feature freeze, even
>> if it does not involve fixing a bug?
>>
>> (2) When adding new tests (e.g. in the course of fixing a bug or
>> increasing test coverage), are we allowed to refactor other
On Thu, Jul 26, 2012 at 6:24 PM, Eli Bendersky wrote:
> You cannot skip the peer review during an RC, no matter how small!
> Even if it is a simple copy-and-paste change, everything requires peer
> review from a core developer.
The extra restrictions during RC are more about not doing things
Am 25.07.2012 16:38, schrieb Guido van Rossum:
> Beware, people requesting dates BC rarely know what they are asking
> for. (E.g. Jesus wasn't born on 12/25/0001.) The calendrical
> ambiguities are such that representing dates that far in the past is
> better left to a specialized class. Read the o
Will there be more 2.7 bugfix releases, and when the next one?
In other words; if I submit a patch and it is accepted, can I
expect that patch be committed also to the 2.7 branch?
Thanks,
Thomas
Been a long time that I've been here - but still using Python (2.7 now)
more and more...
__
On Thu, Jul 26, 2012 at 10:56 AM, Thomas Heller wrote:
> Will there be more 2.7 bugfix releases, and when the next one?
>
> In other words; if I submit a patch and it is accepted, can I
> expect that patch be committed also to the 2.7 branch?
>
>
We are still back-porting bug fixes to 2.7 branch.
Will there be more 2.7 bugfix releases
Yes.
and when the next one?
That's up for Benjamin to decide. My view is that one bugfix
release every year is more than enough.
In other words; if I submit a patch and it is accepted, can I
expect that patch be committed also to the 2.7 branch?
Don
Am 26.07.2012 20:16, schrieb mar...@v.loewis.de:
Will there be more 2.7 bugfix releases
Yes.
and when the next one?
That's up for Benjamin to decide. My view is that one bugfix
release every year is more than enough.
Ok. I expect we will still be using 2.7 next year in my company.
In o
On 7/26/2012 2:50 PM, Thomas Heller wrote:
Am 26.07.2012 20:16, schrieb mar...@v.loewis.de:
Don't you have commit rights still?
I dont't know.
The tracker thinks you do. That is what the Python logo next to your
name means.
Anyway, I do know nearly nothing about hg and don't have time
Am 26.07.2012 09:59, schrieb Chris Withers:
> Hi All,
>
> Sorry if this is considered slightly off topic, but Sphinx is the tool
> we use for the Python core docs so:
>
> Who's looking after Sphinx nowadays? I've hit what I consider to be a bug:
>
> https://groups.google.com/group/sphinx-dev/br
Hi Georg,
On 26/07/2012 21:07, Georg Brandl wrote:
If you're patient enough, I'll take care of your problem eventually.
If not, and you're looking for a project to co-maintain, we can set
something up :)
I'm certainly interested in helping out where I can, Sphinx has been a
fantastic tool...
Am 26.07.2012 10:24, schrieb Eli Bendersky:
>>> I have a few questions about feature freeze:
>>>
>>> (1) Is increasing test coverage acceptable during feature freeze, even
>>> if it does not involve fixing a bug?
>>>
>>> (2) When adding new tests (e.g. in the course of fixing a bug or
>>> increasin
12 matches
Mail list logo
