On 3/21/07, Facundo Batista <[EMAIL PROTECTED]> wrote:
> So, as a resume of the choices we still need to settle:
>
> a) Repeat the same functionality in 5 other libraries
> b) Write the function in socket.py, public
> c) Write the function in socket.py, non public
The fact that it's needed in 5 places in the stdlib suggests that
there's plenty of user code that could benefit from it too. Hence, I
prefer (b), but if that really freaks people out, I'm okay with (c)
too. I'm not okay with (a).
Thanks, by the way, for creating this patch (and updating it based on
python-dev feedback). I think it's really important for the
maintainability of Python that duplicate code is factored out whenever
possible.
STeVe
--
I'm not *in*-sane. Indeed, I am so far *out* of sane that you appear a
tiny blip on the distant coast of sanity.
--- Bucky Katt, Get Fuzzy
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
