holiday here,
and so that's the day that's most likely for me...
Sounds good to me. Anything in that range is equally doable.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org
--
Fred L. Drake, Jr. fdrake at acm.org
___
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
will be convinced that the file is still
open and refuse to let you delete it. To fix that, you'd have to trigger GC
from the failed removal operation and try again.
I think we'd find there are a lot more operations that need that support than
we'd like to think.
-Fred
--
Fred L. Drake, Jr
be conservative in what we generate.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
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
()
suffices for that much. Tack on .replace('-', '') to do the whole job.
Yep, that would work too.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
the range of what's accepted and produced by the
various XML-RPC libraries, but I've not looked hard for it.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python
-Encoding field should be
included. There should also be a field for the version of Python that's
required.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo
or on a project web page. A proper field
will be added for this in the future (hopefully not too distant).
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python
). Getting the metadata wrong is
just too evil. Now that more people have seen the code for PyPI (and
understand more of it), it'll be easier to implement new fields once they've
been carefully defined.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
the API, if its useful at all.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
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
, a developer should not find difficulty to
reverse that if needed.
Right. I think if the API provides a control for this and some mention is
made in the documentation, that would be good.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev
platforms, would be helpful.
-Fred
--
Fred L. Drake, Jr.fdrake at acm.org
___
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
to describe them. So Python 2.2.2 can become Python 2.2.2
(unmaintained). Whether this is desirable or not, I'm not sure.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman
categories/groups were marked unusable for new submissions. But
that's not necessary in any way.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
On Thursday 30 June 2005 17:26, Raymond Hettinger wrote:
the current idiom:
mylist[:] = [] # clear
Unless you happen to prefer the other current idiom:
del mylist[:]
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python
, with this link to the specific PEP
section, so that we can get this fixed.
Unless, of course, you have the time and inclination to finish it off
yourself. :-)
(I know, I've not been very helpful getting doc issues cleared up lately; I'm
hoping that'll get a bit better soon.)
-Fred
--
Fred L. Drake
On Tuesday 05 July 2005 02:57, Greg Ewing wrote:
I'm thinking about something like context manager,
or at least something with context in it.
Oh, I like this one. Context manager / context protocol work well for me.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
such low-hanging fruit is worthwhile.) What do other people think?
The low-hanging fruit, of course, is to close the report with a 'reject'
status.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
away.
Yes, it does. Avoiding the maintenance burden is a matter of having only one
source for the docs, and doesn't not inform the selection of which place is
best in a substantial way. A little though.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
to keep multiple
projects in a single repository for zope.org.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org
not sure if there are any political issues about that, but I
think everyone actively developing on that project has been happy with the
move. (Only the berlios.de Subversion is being used; everything else remains
at SourceForge IIRC.)
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
can provide more details of what he had to do; I was only
slightly involved in the discussions.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
convert our trunk, which took several hours. The main time
sink was in the load step of the conversion process.
This might be a possibility for Python as well, though we have a much less
complex branching structure, so the conversion may not be so difficult.
-Fred
--
Fred L. Drake, Jr
with them generically if they can reasonably want to deal with either), then
it seems they need a common base:
+--AnyDeprecationWarning
+--DeprecationWarning
+--PendingDeprecationWarning
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
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
. That makes it a child of Raisable, not Error.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
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
won't deal with the varargs
portion of the signature, but it can deal with the return value and normal
arguments without worrying about varargs portions of the signature for any
function.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python
now. :-)
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
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
to be raised and
then caught again abstractly, in addition to allow anydbm.error to act as a
base exception that catches the specific errors raised by the backend
databases.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing
On Tuesday 30 August 2005 11:26, Raymond Hettinger wrote:
FWIW, I am VERY happy with the name partition().
I like it too. +1
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http
. :-)
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
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
with this in
the next 5 minutes. Sorry. I do intend to read your message carefully and
respond then.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe
.
That's what strikes me as different in this discussion.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org
discussion here just now leads me to believe that at least two of us
here (including myself) think iterators shouldn't have length at all: they're
*not* containers and shouldn't act that way.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev
releases.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
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
.
Well stated. I'm in complete agreement on this matter.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman
--
Fred L. Drake, Jr. fdrake at acm.org
___
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
. Dates and times, separate from a date-time, are
completely unsupported by the bare XML-RPC protocol. Applications must
determine what they mean and how to encode them in XML-RPC separately if they
need to do so.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
as quickly as
possible, but it's a manual process just to get the mail through.
We should probably have a dedicated address for this, or tell people to send
them to webmaster.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing
-deposit address be routed to the webmaster
crew? Most of the webmasters don't have the access needed to deposit keys.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman
candidate, because we get the
advantages of peer review.
For things that describe policy, I don't think that's so great. For policy
(how to use SVN for Python development, because we have certain rules), I
think we want to maintain strict editorial control.
-Fred
--
Fred L. Drake, Jr. fdrake
, a listing of files that _would_ change if you were to
do svn update.
It's worth noting that svn status -u does require network access, since it
has to check with the repository to see what's been updated there.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
and svn:ignore.
Shouldn't we simply remove the .cvsignore files? Subversion doesn't use them,
so they'll just end up getting out of sync with the svn:ignore properties.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev
On Sunday 30 October 2005 18:37, Gustavo Niemeyer wrote:
I'd like to apply the following patch:
+1
Might want to include SystemExit as well, though I think that's less likely to
be seen in practice.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
On Monday 28 November 2005 20:14, 장혜식 wrote:
There's a hacky trick to remove them:
put rm -rf $CVSROOT/src into CVSROOT/loginfo
and remove the line then and commit again. :)
Wow, that is tricky! Glad it wasn't me who thought of this one. :-)
-Fred
--
Fred L. Drake, Jr. fdrake
time.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
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
no longer be used as we have now migrated to CVS on Sourceforge :-(
Try it now.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http
: vwrite_tuple: Assertion `opt
|| cstr' failed. Aborted
I've never seen anything like that from Subversion before.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo
to each version.
I think the whole PyXML v. the standard library dabacle has taught us that
there should *always* be an explicit path to each version of a module or
package.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
belongs on the Doc-SIG; I've CC'd that
list.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python
.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
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
it to me for conversion. I do not want
LaTeX itself to cause us to lose documentation contributions; the hard part
for documentation really is getting good content. Hard workers shouldn't be
turned away. :-)
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
make sure it's easy for everyone to contribute. I'm
certainly interested in suggestions, though I make all of them happen.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org
): please make a note of this in your next summary. The
I-can't-contribute-because-I-don't-know-LaTeX notion has to die, die, die.
An excellent idea!
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
. :-)
In general, my worry is less with dealing with spam than with ensuring
integration of content enhancements before release candidates go out.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http
; dynamic DNS is fine if the name propogation to the
slaves is fast). The slaves do not need to be reachable from the buildbot
master, since the slave is responsible for contacting the master.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python
On Tuesday 27 December 2005 08:06, Fredrik Lundh wrote:
the trunk link on
http://www.python.org/dev/doc/
Fixed now; thanks for the reminder.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev
On Friday 30 December 2005 06:31, Ka-Ping Yee wrote:
Is there a really good reason to do that? It's not obvious to me.
No more than there is to rename None to none or NONE.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing
unmark
the test. This avoids having to refactor test classes just to update the
status of a test.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
?
I had a class to do the really-careful editing bit like Guido described once,
but lost it in a disk crash several years ago. I really wish I'd gotten that
into revision control somewhere, but it's too late now. I've not needed that
badly enough to re-write it.
-Fred
--
Fred L. Drake, Jr
; mirroring the exact form
of the word fail doesn't make sense; making it readable does.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe
already included in the urlparse module is a URN scheme from
CNRI. Either we should support URNs, or we should consider deprecating
support for that one.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
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
and time on an impossible quest.
+1
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
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
.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
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
; PageRank(tm) numbers don't get
transferred as quickly as contents. I have this worry too in the
context of the python.org redesign; 301 permanent redirect is *not*
going to help PageRank of the new page.)
Maybe I'm just not getting why that's relevant.
-Fred
--
Fred L. Drake, Jr
, 1, 2, 3])
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
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
L. Drake, Jr. fdrake at acm.org
___
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
. python-dev topics occaissionally pop up for me, but time has been
too limited to get back to the important items, like this one.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http
I've actually dealt
with where I wanted a variation of a mapping with default values.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe
comes up, but not the only one.
and in the process breaking an important
quality of good Python code, that attribute and getitem access not have
noticeable side effects.
I'm not sure that's quite as well-defined or agreed upon as you do.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
to that on
buildbot.zope.org as well? ;-) The improved use of horizontal space is
good.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
On Sunday 19 February 2006 18:07, Walter Dörwald wrote:
How about this one:
http://styx.livinglogic.de/~walter/python/BuildBot_%20Python.html
Sigh. This is nice too. Now I'm not sure which I'd rather see on
zope.org. ;-)
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
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
Eastern time).
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
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
obviously goes under Structured Markup Processing Tools.
Yes to both.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http
components).
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
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
--
Fred L. Drake, Jr. fdrake at acm.org
___
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
On Wednesday 29 March 2006 00:48, Fred L. Drake, Jr. wrote:
I think the existing usage for classes is perfectly readable. The
@-syntax works well for functions as well.
On re-reading what I wrote, I don't think I actually clarified the point I was
trying to make originally.
My point wasn't
On Wednesday 29 March 2006 21:55, Greg Ewing wrote:
import db where db.stdlib == True and db.language == SQL \
and db.interface == DBAPI2.0
While we're at it, we could spell import select. :-)
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
and the def; having class decorators embedded within the class should still
allow the docstring to be the first thing, so there's more distance between
the decorator and the name being decorated. The extra hint about what's
being decorated is nice.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
On Monday 03 April 2006 14:45, Guido van Rossum wrote:
Could one of the tracker admins add a Python-3000 group to the SF
trackers (while we're still using them :-)? This is so we can easily
move proposals between Python 3000 and Python 2.x status.
Done.
-Fred
--
Fred L. Drake, Jr
--
Fred L. Drake, Jr. fdrake at acm.org
___
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
On Thursday 06 April 2006 18:09, Georg Brandl wrote:
a while ago, Raymond proposed str.partition, and I guess the reaction
was positive. So what about including it now?
+1
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing
On Friday 14 April 2006 06:35, Andrew Clover wrote:
Files and preview here:
http://doxdesk.com/img/software/py/icons2.zip
http://doxdesk.com/img/software/py/icons2.png
Very nice!
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
when Fred added it.
Looks like a bug to me. It should be set just before confstr() is called.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
for that as well as
your implementation efforts.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
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
] Error 255
make[1]: Leaving directory `/home/fdrake/projects/python/trunk/Doc/info'
make: *** [info] Error 2
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo
have tests that do this. This is a very real use case.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman
isn't the new
behavior, but the change in the behavior. That's certainly it for me.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe
of these modern desktops
just to get all the pretty pictures.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org
dependencies on the specific signature of the
function. In a subsequent version of the function, the function is
determined to need additional information. The only way to add an
argument is to use a keyword for which there is no positional
equivalent.
-Fred
--
Fred L. Drake, Jr
, and the WeakValueDictionary gains
the .itervaluerefs() and .valuerefs() methods.
The patch includes tests and docs.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
`valuerefs`
implementation to weed out weakrefs whose referents are already gone:
the caller has to make this check anyway when it iterates over the
Good point; I've updated the patch accordingly.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
On Tuesday 02 May 2006 22:32, Guido van Rossum wrote:
and '@deco').
Pronounced at-deck-oh, @deco is an art-deco variant favored in r-deprived
regions.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev
, and
- why we'd use it with a string and an int.
I see possibilities here. :-)
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http
releases.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
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
will be there.
I'd rather not propogate the pain caused xml package insanity any further.
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http
on the old behavior,
I'll be glad to look at the problems. I expect to have some time in the next
few evenings, so I should be able to look at these soon.
Is the SourceForge CVS the definitive development source for the feed parser?
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
On Monday 12 June 2006 13:42, Guido van Rossum wrote:
Maybe we
should get serious about slimming down the core distribution and
having a separate group of people maintain sumo bundles containing
Python and lots of other stuff.
+1
-Fred
--
Fred L. Drake, Jr. fdrake at acm.org
1 - 100 of 168 matches
Mail list logo
