Python Worst Practices

Fri Feb 27 16:40:31 EST 2015

On Sat, Feb 28, 2015 at 8:37 AM, Dave Angel <davea at davea.name> wrote:
> Right. In C and C++, instead of being the first slide, it'd be the first 3
> or 4. Between header file conflicts (especially good because the stdlib
> itself has many multiply-defined symbols, duplicate header files, and
> contradictory include path patterns)

Yeah, Python has some issues with sys.path and how your local module
can unexpectedly shadow a stdlib one, but at least the stdlib itself
doesn't have any conflicts. I should not ever have to do this dance:
#include <somefile.h>
#undef SOME_SYMBOL
#include <otherfile.h>
But sadly, I do.
ChrisA