[Python-Dev] Unittest PEP do's and don'ts (BDFL pronouncement) (original) (raw)
Raymond Hettinger python at rcn.com
Thu Jul 17 04:09:24 CEST 2008
- Previous message: [Python-Dev] Unittest PEP do's and don'ts (BDFL pronouncement)
- Next message: [Python-Dev] Unittest PEP do's and don'ts (BDFL pronouncement)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I'd quote “Practicality beats purity”, but I'm not even sure if it is purity that you have in mind.
From: "Ben Finney" <ben+python at benfinney.id.au>
Close: I'm interested in keeping camel's noses out of tents.
I have no idea what you mean or are trying to accomplish (unless the camel's nose refers to camelcase).
You could always just fork the unittest module and see if the masses flock to your version. That way at least people will have a choice about whether to accept these new design proclivities.
Raymond
- Previous message: [Python-Dev] Unittest PEP do's and don'ts (BDFL pronouncement)
- Next message: [Python-Dev] Unittest PEP do's and don'ts (BDFL pronouncement)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]