final question: logging to stdout and updating files
Ramchandra Apte
maniandram01 at gmail.com
Fri Oct 5 09:32:28 EDT 2012
More information about the Python-list mailing list
Fri Oct 5 09:32:28 EDT 2012
- Previous message (by thread): final question: logging to stdout and updating files
- Next message (by thread): final question: logging to stdout and updating files
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thursday, 4 October 2012 19:30:26 UTC+5:30, Steven D'Aprano wrote: > On Thu, 04 Oct 2012 06:34:28 -0700, Ramchandra Apte wrote: > > > > > "Optimize code always even if it causes bugs" - Ramchandra Apte, 2001- > > > > Well, you've just added yourself into my list of people whose advice > > should always be ignored. > > > > That is *terrible* advice. But if you insist on following it, you can > > optimize *any* Python program to this: > > > > # === start code === > > pass # this line is optional > > # === end code === > > > > > > There you go. The most heavily optimized, fastest Python program in > > existence. Sure, it has a few bugs, but boy is it fast!!! > > > > > > -- > > Steven Please disclose the list of people. This email is subject to important disclosures available at loobafoobajo.ke/legal.html LOOBA FOOBA JOKE COMPANY MAKES NO WARRANTIES ABOUT THIS EMAIL Read at your risk - you may die from reading this email. ;-P
- Previous message (by thread): final question: logging to stdout and updating files
- Next message (by thread): final question: logging to stdout and updating files
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list