merits of Lisp vs Python

[Bill Atkins]

Pascal Bourguignon <pjb at informatimago.com> writes:

>> This is true, but now someone
>> has to intentionally and specifically import the package containing
>> that shadowed + into their own package.  You are never unwittingly
>> using a different + than the standard CL one, although you really seem
>> to want this to be the case.
>
> The Common Lisp standard has no provision to and indeed forbid to
> modify the function binding of the COMMON-LISP:+  symbol.

I'm not talking about redefining the + symbol; I'm talking about
shadowing it and defining a new function on a different symbol that
has the same symbol-name.