[Python-Dev] PEP 385: the eol-type issue (original) (raw)
Mark Hammond skippy.hammond at gmail.com
Wed Aug 5 13:46:14 CEST 2009
- Previous message: [Python-Dev] PEP 385: the eol-type issue
- Next message: [Python-Dev] Reasons for using expy
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 5/08/2009 9:28 PM, Dirkjan Ochtman wrote:
On Wed, Aug 5, 2009 at 13:19, Mark Hammond<mhammond at skippinet.com.au> wrote:
Configuring on each clone would certainly be sub-optimal, so the proposal is this configuration be stored in a versioned file in the repo. Even if we do that, enabling hg extensions will still need to be done locally -- although it can be done per-user/box instead of per-clone.
That is completely fine, and not unlike SVN where a per-user/box setting generally needs to be set once - but after that everything "just works". Windows developers don't mind taking a hit once ;) The dev guide can make it clear what the expectations are...
Cheers,
Mark
- Previous message: [Python-Dev] PEP 385: the eol-type issue
- Next message: [Python-Dev] Reasons for using expy
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]