martin(a)v.loewis.de (Martin v. Loewis) writes:
> Sve <Sve(a)softserv.attunity.co.il> writes:
> > Can You pls help us with extended python on Open VMS platform.
> No. python-help is for the discussion of the future development *of*
Martin meant python-dev here...
> Python, not for the development *with* python. Please use
> python-list(a)python.org instead.
This bit is still right.
FORD: Just pust the fish in your ear, come on, it's only a
-- The Hitch-Hikers Guide to the Galaxy, Episode 1
Can You pls help us with extended python on Open VMS platform.
We already extended python on NT (with DLL).
How we have to create same C code on Open VMS.
Attunity Software ServicesLtd.
t +972-4-990-9966 ext.114
Just a quick note to let folks know that David Goodger has joined the
PEP editors. He'll be doing most of the editor's work, but I'll still
provide backup help as necessary. This should greatly improve the
responsiveness of the PEP editors <wink>.
Please continue to use peps(a)python.org for all correspondence about
the PEPs, as this will reach both David and myself. Thanks David!
After a long time of inactivity, I hope to be back to some python
hacking. Before getting into any coding, I'd like to discuss with
you some conceptual and boring stuff I have in my mind.
In the past I have given small contributions to the python standard
distribution. Unfortunately (for myself), I slowed down until I stopped
contributing, even though I have a great affect by the interpreter. Now
I realize that one of the reasons I've stopped contributing is because
there's a large inertia in getting stuff reviewed. The reason why this
is happening seems more aparent now that I was off for a while: there's
a small core of very busy developers working on core/essential/hard
stuff *and* in code reviewing as well.
At the same time, I've seen Guido and others bothered a few times
because of the lack of man power. So the question is: how do I, a
developer which feels capable of helping in python's development, can
get some of the tasks which take your time out of your hands? Or even,
how is it possible to improve some part of the development process by
giving people like me some instructions? Also, isn't it easy to point
out what's wrong in a commit from someone who is following the
development process for a while than taking the time to review its code
in the sourceforge patch system?
My feeling is that the Python development is currently overly
centralized, and that you might be suffering from that now, by being
unable to handover some of your tasks to someone else. I feel that
everytime I send a patch, besides being contributing, I'm also
overloading you with more stuff to review and comment and etc. Perhaps
the fallback costs for some wrong commit is too high now (did I heard
someone mentioning subversion?)?!
Could someone please discuss that issues with me, and perhaps just kick
me away saying that I'm crazy? :-)
[ 2AAC 7928 0FBF 0299 5EB5 60E2 2253 B29A 6664 3A0C ]
I was just reading this and it seems
to overlap with: http://www.python.org/peps/pep-0218.html
I.E. uniq is equivalent to union (with self).
wrt to the uniq command line tool, if you've 2 files a & b, then:
uniq a b = union
uniq -u a b = difference
uniq -d a b = intersection
So uniq really is a set operation and if Python had
a set builtin type then I'm not sure a uniq method
would be required? Perhaps the list object could
support the union operator so to uniqify a list you
mylist |= mylist
I've downloaded and formatted the 325 bugs in SF.
Here's a breakdown of bugs by category (before I changed
some of the Nones to an appropriate category):
Demos and Tools 8
Extension Modules 15
Python Interpreter Core 26
Python Library 78
Regular Expressions 14
Type/class unification 8
There's more detail available in html format here:
gnumeric file here:
text (tab separated) here:
The info shown is: SF id #, Summary, Date Submitted,
Assigned To, Submitted By, Category, Comments, Date of Last Comment.
Current sort criteria is by Category, then by Date Submitted.
Bugs fall into many categories including: platform specific,
duplicates (e.g., RE max recursion), cannot be reproduced,
believed to be fixed, but the submitter has not verified the fix,
feature requests, and of course plain bugs.
I may try to work up another list of the bugs which are
almost fixed. Meaning, bugs which need verification
or have a proposed fix attached.
It would be great if people could go through topics
of interest to them and help fix problems in that category.
Many of the bugs in the 'Python Library' are web related
(ie, cgi, htmllib, urllib, etc).