Re: Python Worst Practices

References	<mclca6$iie$1@ger.gmane.org> <7053A277-9687-49B0-9FDB-CB4DB3E76DEC@gmail.com> <54F0E38D.40006@davea.name>
Date	2015-02-28 08:40 +1100
Subject	Re: Python Worst Practices
From	Chris Angelico <rosuav@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.19321.1425073235.18130.python-list@python.org> (permalink)

Show all headers | View raw

On Sat, Feb 28, 2015 at 8:37 AM, Dave Angel <davea@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

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: Python Worst Practices Chris Angelico <rosuav@gmail.com> - 2015-02-28 08:40 +1100

csiph-web