Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #86596 > unrolled thread

Re: Python Worst Practices

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

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

#86596 — Re: Python Worst Practices

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

[toc] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web