lissacoffey added the comment:
I measured both the total time of the run, the time to process each input
records, and time to execute just the seek() call for each record. The bulk of
the per-record time was in the call to seek(), so by reducing that time, I sped
up my run-times significantly
lissacoffey added the comment:
This bug is a really annoying one, any chance it will be fixed in 2.7? It's
really a matter when you want to deploy a program using distutils (my case),
because you cannot really require your clients to edit the registry themselves
:/
Thanks
lissacoffey added the comment:
Using an environment variable is not the holy grail for this. On writing a
non-single-user application you can't expect the user to set extra environment
variables.
If compatibility is the only reason in my opinion it would be much better to
include some
lissacoffey added the comment:
On the other hand, the way imports are handled in 3.3 and later is a bit
different, and if I run the unit test (which does still fail for me on 2.7 tip)
on 3.3 and 3.4 tip it passes.
Thanks
Lisa - python expert
mysite: http://www.followthesteps.net/sky-contact
lissacoffey added the comment:
How about Python grows a additional btree implementation in its collections
module? I know that it's not going to fix existing code. However in the long
run it's the best safeguard against hash collision attacks. I'm thinking about
a simple, self