"Fredrik Lundh" <fredrik at pythonware.com> wrote:
> Duncan Booth wrote:
>>> No it isn't Pythonic.
>> rubbish. using a single constructor that handles two common use cases is
> perfectly Pythonic (especially if you're targeting casual programmers).
>Yes, but I don't think that the specific case the OP asked about would be
pythonic: there was no need two separate calling conventions there.
