On 24/03/2011 03:02, Mark Hammond wrote:
On 24/03/2011 1:20 PM, Michael Foord wrote:
On 24/03/2011 00:44, Dj Gilcrease wrote:
On Wed, Mar 23, 2011 at 8:14 PM, Mark
Hammond wrote:
If you guys (or anyone) would like to agree on some precise rules for
both
the location of the config file and its
On 24/03/2011 1:20 PM, Michael Foord wrote:
On 24/03/2011 00:44, Dj Gilcrease wrote:
On Wed, Mar 23, 2011 at 8:14 PM, Mark
Hammond wrote:
If you guys (or anyone) would like to agree on some precise rules for
both
the location of the config file and its contents and express this as
a patch
to th
On 24/03/2011 00:44, Dj Gilcrease wrote:
On Wed, Mar 23, 2011 at 8:14 PM, Mark Hammond wrote:
If you guys (or anyone) would like to agree on some precise rules for both
the location of the config file and its contents and express this as a patch
to the PEP text, I have no problem supporting it
On Wed, Mar 23, 2011 at 8:14 PM, Mark Hammond wrote:
> If you guys (or anyone) would like to agree on some precise rules for both
> the location of the config file and its contents and express this as a patch
> to the PEP text, I have no problem supporting it in the implementations.
> I'd like to
On 24/03/2011 4:34 AM, Ethan Furman wrote:
Michael Foord wrote:
To be honest I would be happy with registry entries instead as the
alternative implementations can then add to their installers (or
provide a script) to add the right registry entry.
I'm partial to the config file method myself. I
On 23/03/2011 01:30, Mark Hammond wrote:
On 23/03/2011 6:12 AM, Michael Foord wrote:
On 22/03/2011 07:21, Mark Hammond wrote:
Hi all,
I've made some changes to the draft PEP and checked it into the PEP
repository as PEP397. The reference implementation is currently being
tracked at http://bugs.
Michael Foord wrote:
To be honest I would be happy with registry entries instead as the
alternative implementations can then add to their installers (or provide
a script) to add the right registry entry.
I'm partial to the config file method myself. I have this vague hope
where this tool cou
On Wed, Mar 23, 2011 at 10:39 AM, Ethan Furman wrote:
> Mike Driscoll wrote:
>>
>> On Tue, Mar 22, 2011 at 2:12 PM, Michael Foord
>> wrote:
>>>
>>> On 22/03/2011 07:21, Mark Hammond wrote:
>>>
>>> Hi all,
>>> I've made some changes to the draft PEP and checked it into the PEP
>>> repository as P
Mike Driscoll wrote:
On Tue, Mar 22, 2011 at 2:12 PM, Michael Foord
wrote:
On 22/03/2011 07:21, Mark Hammond wrote:
Hi all,
I've made some changes to the draft PEP and checked it into the PEP
repository as PEP397. The reference implementation is currently being
tracked at http://bugs.python
On 23/03/2011 14:52, Mike Driscoll wrote:
On Tue, Mar 22, 2011 at 2:12 PM, Michael Foord
wrote:
On 22/03/2011 07:21, Mark Hammond wrote:
Hi all,
I've made some changes to the draft PEP and checked it into the PEP
repository as PEP397. The reference implementation is currently being
tracke
On Tue, Mar 22, 2011 at 2:12 PM, Michael Foord
wrote:
> On 22/03/2011 07:21, Mark Hammond wrote:
>
> Hi all,
> I've made some changes to the draft PEP and checked it into the PEP
> repository as PEP397. The reference implementation is currently being
> tracked at http://bugs.python.org/issue116
On 23/03/2011 6:12 AM, Michael Foord wrote:
On 22/03/2011 07:21, Mark Hammond wrote:
Hi all,
I've made some changes to the draft PEP and checked it into the PEP
repository as PEP397. The reference implementation is currently being
tracked at http://bugs.python.org/issue11629.
Hey Mark,
One w
On 22/03/2011 07:21, Mark Hammond wrote:
Hi all,
I've made some changes to the draft PEP and checked it into the PEP
repository as PEP397. The reference implementation is currently being
tracked at http://bugs.python.org/issue11629.
Hey Mark,
One way of supporting alternative implementa
13 matches
Mail list logo
