Because scientists, financial analysts, web designers, etc all have
different needs.
My point is just that a web designer probably doesn't care if he's
got numpy, nor does a mathematician care if he has cherrypy
onboard. They only care when the tools they need aren't there,
which is
Well... a middle ground certainly could exist; perhaps in the form of an
Extended Standard Library (community distribution), with simple
installation and management tools.
It could be blessed by python-dev and maintain a high standard (only well
established best-of-breed modules with a
I don't think I'm understanding you correctly in that thread then, ISTM
that you're advocating better packaging systems as an alternative to
this. Would you mind clarifying?
Gladly.
In my mind, 'better packaging' is not just about something that will let
you do 'pypkg install foo' and
This link has all post concatenated together in reverse order of how they
should be read. The tags link returns the same page. Does your blog software
allow you to make a master post and update with new links as available?
Ugh, either it doesn't or I couldn't find the feature (I'm using
Hi,
I wanted to let python-dev know about a series of articles about CPython's
internals I'm publishing under the collective title Guido's Python* (
http://tech.blog.aknin.name/tag/guidos-python/). Three articles already were
published already, more are planned (mainly focused on CPython/py3k,
So I'm thinking either we make an
immutable/hashable dict while we're at it, or store the keyword
arguments as a tuple (which guarantees immutability), and only
convert them back to a dict when you want to call the partial object
(simpler, slower).
I'd support an immutable dict. [...]
I'm never certain where to reply in such a case, on the list or on the
issue, but since no one is nosy yet to Daniel's patch, I thought I'd ask
here.
While a partial object should reasonably never change, you could change it:
from functools import partial
p = partial(lambda *a, **kw: kw, 1, 2,
Yes, in the last year in particular there has been some excellent effort
of maintaining the issue tracker content. But the question still remains
- who are we worried about offending?
The people who are potential new contributors but don't currently know
anyone in the Python community.
By
Issue #7978 (http://bugs.python.org/issue7978) describes a bug in
SocketServer where a received signal in SocketServer's select() call
will raise an uncaught exception due to EINTR. The proposed solution
was to wrap SocketServer's select() with something like twisted's
untilConcludes function,
