Michal Vitecek wrote: > Michael Hudson wrote: > >>> okay - i did as you said and the speed-up is only 2.1% so it's not >>> probably worth it. here come the numbers: >> >>I didn't say "*two* point one", I said "*nought* point one"!: > > crap. i found the problem - on a _completely unused_ computer the > difference is indeed only ~0.7%. my apologies for false alarm :/ I'd rather suggest to take a look at making more use of the available Python macros in the interpreter. Things like PyInt_AsLong() can often be written as PyInt_AS_LONG() because there's a type check only a few lines above the call. -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, Mar 13 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ Python UK 2003, Oxford: 19 days left EuroPython 2003, Charleroi, Belgium: 103 days left
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4