On Fri, Aug 6, 2010 at 2:25 AM, LD 'Gus' Landis wrote:
> Hi,
>
> I just read an interesting article (interview with Fred Brooks).
> See: http://www.informit.com/articles/article.aspx?p=1600886
>
> Eoin: The book contains a lot of explicit and implicit advice for those
> who must manage design
Hi,
I just read an interesting article (interview with Fred Brooks).
See: http://www.informit.com/articles/article.aspx?p=1600886
Eoin: The book contains a lot of explicit and implicit advice for those
who must manage design projects. What would your top three pieces
of advice for such
Barry Warsaw wrote:
Wait. It's a joke?!
Probably, but it's also useful behaviour -- I hope
it stays!
(Not that I would ever presume to use it in any
code inflicted on anyone else, but it's nice to
know I have a choice in the privacy of my own
computer.)
Heil-the-FLUFl-ly,
Greg
_
Barry Warsaw writes:
> On Aug 04, 2010, at 06:48 PM, Jasper St. Pierre wrote:
> >hmm... BARRY_AS_BDFL and barry_as_FLUFL
> [...]
>
> >nothing noticable happened. I googled the latter, and found that it's
> >an April Fools (of 2009!) checkin that was never reverted.
>
> Wait. It's a joke?!
That
On Aug 04, 2010, at 06:48 PM, Jasper St. Pierre wrote:
>hmm... BARRY_AS_BDFL and barry_as_FLUFL
[...]
>nothing noticable happened. I googled the latter, and found that it's
>an April Fools (of 2009!) checkin that was never reverted.
Wait. It's a joke?!
signature.asc
Description: PGP signatur
On Wed, Aug 4, 2010 at 3:48 PM, Jasper St. Pierre wrote:
> I was fooling around with Python 3.1 today, and I found this little nugget:
>
import __future__
dir(__future__)
> ['CO_FUTURE_ABSOLUTE_IMPORT', 'CO_FUTURE_BARRY_AS_BDFL',
> 'CO_FUTURE_DIVISION', 'CO_FUTURE_PRINT_FUNCTION',
> 'CO_
Hello
> hmm... BARRY_AS_BDFL and barry_as_FLUFL
Oh, bad consistency. Should have been BARRY_AS_FLUFL and barry_as_flufl.
from __future__ import barry_as_FLUFL
> nothing noticable happened.
I made some tests about that and found that the behavior didn’t match
the PEP; I have to redo experi
I was fooling around with Python 3.1 today, and I found this little nugget:
>>> import __future__
>>> dir(__future__)
['CO_FUTURE_ABSOLUTE_IMPORT', 'CO_FUTURE_BARRY_AS_BDFL',
'CO_FUTURE_DIVISION', 'CO_FUTURE_PRINT_FUNCTION',
'CO_FUTURE_UNICODE_LITERALS', 'CO_FUTURE_WITH_STATEMENT',
'CO_GENERATOR_A
