Must... control... credit card! :)
(see this link)
Thursday, November 27, 2008
Monday, November 24, 2008
Python - list clearing?!!
Today's trick question: How do you clear a list in python?
Not by .clear(), as you do with other python containers set or dicts (or _any_ in C++/Java/whatnot).
Nonono, you assign the entire slice of the list to the empty list, or delete the whole slice!
mylist[:] = []
del mylist[:]
.. .. .. .. Arrghh!!!!
Why do I have to learn the slice syntax, and the fact that there is a slice of the whole pie, and that I can assign a list to a slice, just to clear the list?!
Appending, concatenating and clearing are simple & common ops, that should be represented clearly and simply. Slicing is advanced, and when I want to do slicing, I read up on it, but I should need it for that. It's like requiring someone to learn discrete integration just to do addition; valid but only correct in the very bad technically-correct kind of way.
(And no, just assigning the empty list to it does not work, as that rebinds the name, it does not change the original list. I have no issue with that, as it's all pointers/references everywhere.)
Apparently, they haven't fixed this in Py3k either.
Looking through forums where this appear every month since Python was first created, the sentiment seems to be that since you can do it with slicing, there's no need for another way to do it!
I began to understand why people feel that the python community is regarded as a bit 'frosty' and cold.
I still like python a lot, but ... Bah!
Not by .clear(), as you do with other python containers set or dicts (or _any_ in C++/Java/whatnot).
Nonono, you assign the entire slice of the list to the empty list, or delete the whole slice!
mylist[:] = []
del mylist[:]
.. .. .. .. Arrghh!!!!
Why do I have to learn the slice syntax, and the fact that there is a slice of the whole pie, and that I can assign a list to a slice, just to clear the list?!
Appending, concatenating and clearing are simple & common ops, that should be represented clearly and simply. Slicing is advanced, and when I want to do slicing, I read up on it, but I should need it for that. It's like requiring someone to learn discrete integration just to do addition; valid but only correct in the very bad technically-correct kind of way.
(And no, just assigning the empty list to it does not work, as that rebinds the name, it does not change the original list. I have no issue with that, as it's all pointers/references everywhere.)
Apparently, they haven't fixed this in Py3k either.
Looking through forums where this appear every month since Python was first created, the sentiment seems to be that since you can do it with slicing, there's no need for another way to do it!
I began to understand why people feel that the python community is regarded as a bit 'frosty' and cold.
I still like python a lot, but ... Bah!
patch.exe on vista - the workaround
Vista apparently thinks that any exe with 'patch' in it's name needs to be run with admin priviliges, probably to make a slew of pre-UAC install wizard patches work properly.
But this applies to good old unix:y 'patch' (which I have in windows-form) too!
Argh!
Update 2008-12-13: The patch.exe in the git-for-windows distribution (msysgit) seems to have the correct magic bits set to allow it to run without UAC getting in the way. So, try replacing your gnuwin32-patch (or whatever you're using) with that.
If that's not an option, here's how to do a workaround:
The trick is to rename patch.exe to pootch.exe (or whatever fancies you) and create a batch file call patch.cmd, with this content:
@"%~dp0\pootch" %*
That makes it work.
(I learn this when running the unit tests of buildbot, a pretty nice tool for distributing automated tests across compilers, computers & os:es!)
But this applies to good old unix:y 'patch' (which I have in windows-form) too!
Argh!
Update 2008-12-13: The patch.exe in the git-for-windows distribution (msysgit) seems to have the correct magic bits set to allow it to run without UAC getting in the way. So, try replacing your gnuwin32-patch (or whatever you're using) with that.
If that's not an option, here's how to do a workaround:
The trick is to rename patch.exe to pootch.exe (or whatever fancies you) and create a batch file call patch.cmd, with this content:
@"%~dp0\pootch" %*
That makes it work.
(I learn this when running the unit tests of buildbot, a pretty nice tool for distributing automated tests across compilers, computers & os:es!)
Monday, November 17, 2008
No Clutter For You
.. at least not with Python bindings. They use autoconf/automake, and didn't compile well on cygwin either, so I've given up.
QT has some animation options. Maybe those will do instead. :)
QT has some animation options. Maybe those will do instead. :)
Subscribe to:
Posts
(
Atom
)