"/a" is not "/a" ?

Steven D'Aprano steve at pearwood.info
Fri Mar 6 21:48:29 CET 2009

Emanuele D'Arrigo wrote:

> Hi everybody,
> while testing a module today I stumbled on something that I can work
> around but I don't quite understand.

Why do you have to work around it?

What are you trying to do that requires that two strings should occupy the
same memory location rather than merely being equal?

> Why c and d point to two different objects with an identical string
> content rather than the same object?

Why shouldn't they?


More information about the Python-list mailing list