n" and "closed"
> deltas is already quite an achievement and shows that our triage works.
Agreed.
We did have negative open deltas for several weeks running in October.
Kudos to everyone involved, and lets do it some more :) I&
resolved soon.
FYI bugs.python.org and www.python.org are different machines, and
in fact the two machines are not even hosted at the same location.
Valery, I would advise you to submit the patch to bugs.python.org when
it comes back up. Patches posted to this mailing list will in general
On Mon, 08 Nov 2010 17:02:24 +0100, wrote:
> If there is no enormous difficulty in maintaining compatibility, I think
> the usual deprecation process should be followed. We donât know who is
> using pydoc as a library, so letâs play safe and not risk breaking their
> code (especially consider
On Mon, 08 Nov 2010 18:10:17 -0600, Ron Adam wrote:
> def _private_api():
> #
> # Isn't it a good practice to use comments here?
> #
> ...
IMO, no.
--
R. David Murray www.bitdance.com
__
ode to deal with.
I think Tres was referring to certain packages (which shall remain
nameless since I don't feel like googling to find one) whose
documentation recommends the 'from import *' methodology.
At least that's how I read "Module writers who..." (that is,
s.python.org/issue1553375
--
R. David Murray www.bitdance.com
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/
r this list. The question was "why did you developers drop this
(obscure) feature that we depend on in Python3?" I don't think that
question would make sense on python-list. Granted, there's a fuzzy
line there, but pylint is really development infrastructure :)
The pyth
processing of non-RFC conformant data.
I want to look at the CGI issue, but I'm not sure when I'll get to it.
--
R. David Murray www.bitdance.com
___
Python-Dev mailing list
Python-Dev@python.org
http://
ng written the above, I googled for UCS-2 and got the Wikipedia
article on UTF16/UCS-2 [1]. Scanning that article, I do not see anything
that would clue me in to the problems of slicing strings in a Python
narrow build. Indeed, reading that article with my limited unicode
knowledge, if I were told P
On Sun, 21 Nov 2010 10:17:57 -0800, Raymond Hettinger
wrote:
> On Nov 21, 2010, at 9:38 AM, R. David Murray wrote:
> > I'm sorry, but I have to disagree. As a relative unicode ignoramus,
> > "UCS-2" and "UCS-4" convey almost no information to me, and the
On Sun, 21 Nov 2010 19:59:54 -0800, Glenn Linderman
wrote:
> On 11/21/2010 9:18 AM, R. David Murray wrote:
> > I want to look at the CGI issue, but I'm not sure when I'll get to it.
>
> Actually, since this code was working before 3.x, and if email.parser
> can n
`, the
faq/extending.rst: ... print('UCS4 build')
faq/extending.rst: ... print('UCS2 build')
--
R. David Murray www.bitdance.com
___
Python-Dev mailing list
Python-Dev@python.org
http://m
On Mon, 22 Nov 2010 12:37:59 -0500, Alexander Belopolsky
wrote:
> On Mon, Nov 22, 2010 at 12:30 PM, R. David Murray
> wrote:
> ..
> > For reference, a grep in py3k/Doc reveals that there are currently exactly
> > 23 lines mentioning UCS2 or UCS4 in the docs.
>
> Did
efer Python because it uses smaller and more namespaces
> which are more specific and well defined. If we add email and compression
> functions to bytes, why not adding a web browser to the str?
As MAL says, the codec machinery is a general purpose too
On Fri, 03 Dec 2010 11:14:56 -0500, Alexander Belopolsky
wrote:
> On Fri, Dec 3, 2010 at 10:11 AM, R. David Murray
> wrote:
> ..
> > Please also recall that transform/untransform was discussed before
> > the release of Python 3.0 and was approved at the time, but it
I understand all four
of these to be "versions of xxx that won't raise". I think that's
a reasonable use of the word 'safe', but perhaps there is something
better.
SafeConfigParser doesn't follow that pattern, of course, though it
is perhaps true that it would raise er
7;t at the moment), it seems to make sense from an implementation
standpoint as well.
Like Ãric, I'm not sure what the implications of the existing module
having been released in 2.7 and 3.2 beta are in terms of making such an
API change.
--
R. David Murray
re lots
more out there[*]. I do especially like the fact that there is one in the
stdlib :)
It seems like the status quo is fine. I wouldn't object to it being
made more consistent. I would object to removing the existing cases.
--
R. David Murray www.bit
un directly. In 3.2, this means it will never show up
normally, since you can't even run the .pyc file without moving it out of
__pycache__. Which means 'ddir' is henceforth useful only to those people
who want to package sourceless distributions of the python code. (If
'12,345'
> ...
> >>> "UK says {value:,@uk} and France says
> {value:,@france}".format(value=12345, uk=uk_loc, france=france_loc)
> 'UK says 1,234.5 and France says 1 234,5'
>
> Comments?
There was at least one long thread on this on py
s "actual, expected"... And yet "expected,
> actual" still looks weird to me. :-(
You aren't unique, I feel the same way. But it seems to me that the most
important thing is to be consistent, so that I don't freak out for long.
--
R. David Murray
t; let developers act more quickly on bug reports. I wonder if this output
> really speeds up the process.
>
> Do you have an example bug where this patch helps in finding the precise
> location of a segfault?
How is 'line 29 in g' not more precise
essage. *format* is
> + an ASCII-encoded string.
So, the former, I'd guess :)
--
R. David Murray www.bitdance.com
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/lis
with
the 8th bit set, leaving no room for interpretation. So presumably
you mean it is (treated as) an ISO-8859-1 encoded string, despite the
function name?
--
R. David Murray www.bitdance.com
___
Python-Dev mailing
On Tue, 28 Dec 2010 13:58:24 +0100, Victor Stinner
wrote:
> Le mardi 28 décembre 2010 à 11:40 +0100, "Martin v. Löwis" a écrit :
> > Am 28.12.2010 11:28, schrieb Victor Stinner:
> > > Le lundi 27 décembre 2010 à 23:07 -0500, R. David Murray a écrit :
> &g
On Tue, 28 Dec 2010 10:28:51 +0100, Victor Stinner
wrote:
> Le lundi 27 décembre 2010 à 23:13 -0500, R. David Murray a écrit :
> > > Modified: python/branches/py3k/Doc/c-api/unicode.rst
> > > ==
gt;
>> I believe you mean
>> "struct.pack no longer implicitly encodes unicode to UTF-8",
>> which will be clearer to most people.
>
>Yes, done in r87559
You still have two words swapped. You changed it to
no longer encodes implicitly unicode
but it
g to be maintaining 2.7 for a while, this is
a workflow problem that we *must* solve to make the hg transition
worthwhile. I have no doubt that we will, but I also have no doubt we
need to *solve* it, not just wave our hands. Many thanks to Georg and
Djirkan for
all supports. In other words,
a user of concurrent.futures really needs to tweak their FreeBSD install
to make in fully functional.
There should be a way (through sysctl, presumably) to query the maximum
number of semaphores and skip the relevant tests on that basis.
--
R. David Murray
On Thu, 30 Dec 2010 14:42:48 +0900, "Stephen J. Turnbull"
wrote:
> R. David Murray writes:
>
> > We merge bug fixes to 2.7 on a routine basis. It is the rule rather
> > than the exception, by a long shot.
>
> For bugfixes, of course it's routine. I un
hat it
> > is a SMOP is a concern :)
>
> Sure, but in this crowd, I wouldn't waste a good worry on this
> particular SMOP.
Talent is one thing, available time, as you pointed out about yourself,
is a different matter.
I'm confident we can make this all work. The only qu
sue numbers). Whoops, two of those are mine. I am still
> learning and will try to remember to include it in both log messages and
> NEWS entries.
Heh. I think two of them were mine, and I'm supposed to know better by now.
--
R. David Murray www.b
you are still relatively new to
Python coding it may take longer to do the necessary research to be able
to write the patch).
If you like you can also come hang out on the #python-dev IRC channel
on freenode, where a number of the core developers and other folks
hang out and discuss issues (am
en
out-of-range values were passed to the CRT that other platforms
accepted.
--
R. David Murray www.bitdance.com
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsub
On Mon, 17 Jan 2011 08:33:42 +, Mark Summerfield
wrote:
> from ..Graphics import Xpm
> SVG = 1
>
> I can do the relative import with Python 3.0 and 3.1 but not with
> 3.2rc1:
What about 3.1.3? I wonder if it is related to this issue:
http://bugs.python.org/issue79
new contributor isn't in general going to know when a small change
is controversial without asking *somewhere*, be it a mailing list or
the tracker. Searching the tracker to make sure it hasn't already been
proposed and rejected is, of course, a good id
g and fix that script. Martin hasn't had time to do it,
and I haven't had time to learn enough about rietveld to try.
Getting set up to test tracker patches is distinctly non-trivial,
which is probably why very few people work on it.
--
R. Davi
are not web developers) avoid XML whenever possible, and when
we do have to deal with it we tend to abstract it behind easier to work
with Python code. The obvious exception to that would be web templating
languages, but I personally prefer to avoid those, as well
s and recompile.
I imagine at least some of this is already covered in the dev guide
(I haven't made time to review it yet). If any of it is unclear
to you, please provide feedback so we can improve the guide (which
is new).
--
R. David Murray www.
ils2 component is newly added.
(Antoine: FYI, the place this is edited is http://bugs.python.org/component,
and I don't know anything more than what is explained on that scree :).
--
R. David Murray www.bitdance.com
y using "If every character is a digit, then it is treated as an
> integer, otherwise it is used as a string".
Perhaps you are thinking of http://bugs.python.org/issue7951. Not
directly on point, but related.
--
R. David Murray
ory
instances intact). With bazaar I got in trouble trying to do that,
because the interrelationship between the working copy directories
(and their subsets of the repo?) and the master repo(?) was not clear.
I never did figure out how to make it work, I ended up st
On Tue, 01 Mar 2011 16:26:05 -0500, Eric Smith wrote:
> On 3/1/2011 4:19 PM, Kerrick Staley wrote:
> > Hello,
> > There is a need for the default Python2 install to place a symlink at
> > /usr/bin/python2 that points to /usr/bin/python, or for the
> > documentation to recommend that packagers ensu
ycle management, but I don't
think there is any *fix* other than more people. So, doing followup after
sprints/bug days to help keep contributor enthusiasm going and get some of
them converted into committers is perhaps the best "fix"
other choice, it should provide a /usr/bin/python2 symlink.
Otherwise, it is going to be getting bug reports from users asking
why XYZ script doesn't run.
In short, I don't see any *downside* to providing a /usr/bin/python2
symlink.
--
R. David Murray
t
about this issue before, it is probably worth mentioning sys.executable
somewhere (a footnote?).
But another issue here (and this speaks against the proposal of not
shipping a /usr/bin/python link) is that it is quite possible to write
a script that will run on either python2 or python3.
On Fri, 04 Mar 2011 07:03:08 -0800, Westley =?ISO-8859-1?Q?Mart=EDnez?=
wrote:
> On Fri, 2011-03-04 at 00:54 -0800, Aaron DeVore wrote:
> > On Thu, Mar 3, 2011 at 11:44 PM, Kerrick Staley
> > wrote:
> > > That way, if the sysadmin does decide to replace the installed "python"
> > > file, he ca
s on it won't run on a vanilla
user-install of 2.7.1 or 2.7. But how likely is that scenario compared
to the scenario where a script written for another distro fails to run
because /usr/bin/python2 doesn't exist? I think the balance of the
est way to find them (if
they aren't ignored).
Or if there's some way to configure my personal .hgrc to ignore
those particular ignore lines, that would be fine too :)
--
R. David Murray www.bitdance.com
___
do a rebuild after...and
all of that just takes too long :)
I guess I have some hg hacking in my future, unless someone has already
written extensions for this stuff.
--
R. David Murray www.bitdance.com
___
Python-Dev ma
olor sit amet
> [python-checkins] devguide: Lorem ipsum dolor sit amet
> [python-checkins] devguide (hg_migration): Lorem ipsum dolor sit amet
>
> What we have isn't bad, but I agree with Benjamin that it could be better.
I don't feel strongly about it either way.
--
R. David Mu
I believe the tracker sent an error message to python-dev as a
result of a failed hook execution. If someone with the
power would release that message so we can see what the error
was, I'd appreciate it :)
--David
___
Python-Dev mailing list
Python-Dev@
hersome, and a double underscore name stands out very
> clearly as being part of the infrastructure rather than
> something user-defined.
But directly calling a __xxx__ method in Python is a very
unusual thing to do. It would be extremely odd to have that
be the expected way to call a
or may not be true of unittest, but if it hasn't been
maintained its present utility is questionable so it may be just as
well to delete it.
--
R. David Murray www.bitdance.com
___
Python-Dev mailing list
Python-Dev@
long as we aren't distributing mercurial itself, I don't see
how a script could be a problem. But, then, IANAL.
--
R. David Murray www.bitdance.com
___
Python-Dev mailing list
Python-Dev@python.org
http://ma
branch. You are even less likely to hit a push race by
following that technique, since the time between the pull -u and the
push is minimized.
--
R. David Murray www.bitdance.com
___
Python-Dev mailing list
Python-Dev@py
On Thu, 17 Mar 2011 05:11:23 +0100, Jesus Cea wrote:
> On 17/03/11 04:41, R. David Murray wrote:
> > Dealing with a null merge when someone else has committed between the
> > time I started the merge dance (I always pull just before I start that)
> > and the time I push is
On Thu, 17 Mar 2011 11:26:13 +0100, Georg Brandl wrote:
> Am 17.03.2011 06:14, schrieb R. David Murray:
> > The fun part comes if there are changesets. At this point there
> > are two options: go through each of the branches doing an up/merge/ci,
> > and then pull/push. O
could indeed be a better way to
go for this particular scenario. I'll have to check that out.
--
R. David Murray www.bitdance.com
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinf
On Thu, 17 Mar 2011 13:35:50 +0100, Jesus Cea wrote:
> On 17/03/11 06:14, R. David Murray wrote:
> > Clearly, this procedure is not for everyone
>
> Clearly not :).
>
> So you do a "hg strip" and start over again.
>
> The problem with this is that you
On Thu, 17 Mar 2011 14:33:00 +0100, Antoine Pitrou wrote:
> On Thu, 17 Mar 2011 09:24:26 -0400
> "R. David Murray" wrote:
> >
> > It would be great if rebase did work with share, that would make a
> > push race basically a non-issue for me.
>
> reba
e above sense to worry about.
When I start working on a feature branch I will be working in a separate
clone and will not rebase. But I will probably produce a collapsed
patch when I'm ready to apply to mainline, so the concern with rewriting
On Thu, 17 Mar 2011 16:00:50 +0100, Antoine Pitrou wrote:
> On Thu, 17 Mar 2011 10:50:24 -0400
> "R. David Murray" wrote:
> > On Thu, 17 Mar 2011 14:33:00 +0100, Antoine Pitrou
> > wrote:
> > > On Thu, 17 Mar 2011 09:24:26 -0400
> > > "R.
On Thu, 17 Mar 2011 20:00:29 +0100, Jesus Cea wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 17/03/11 14:45, R. David Murray wrote:
> > Not if the cpython repo is in a fully merged stated. And if it
> > isn't, I will wait until it is. (The update
hrough the
whole thingan issue was submitted for a particular section and I
updated that section and the other one talking about the same topic
(sorry I don't remember which one off the top of my head)).
--
R. David Murray http://www.bitdance.com
__
generated one last
time for its upcoming last bugfix release. It's easy enough (now that we
no longer have to deal with svnmerge) that I've been doing that, myself.
--
R. David Murray http://www.bitdance.com
___
Python-Dev mail
hange.
>
> Anyway, I thought I was supposed to pull from head to 3.2 and 2.7. What is
> "dev"?
That's "doc speak", I guess. http://docs.python.org/dev/library, for
example, points to the library reference for the docs on the default
branch.
--
R. David Murray
On Thu, 17 Mar 2011 14:33:00 +0100, wrote:
> On Thu, 17 Mar 2011 09:24:26 -0400
> "R. David Murray" wrote:
> >
> > It would be great if rebase did work with share, that would make a
> > push race basically a non-issue for me.
>
> rebase as well as str
On Sun, 20 Mar 2011 12:17:25 +0100, Antoine Pitrou wrote:
> Le dimanche 20 mars 2011 à 00:06 -0400, R. David Murray a écrit :
> > On Thu, 17 Mar 2011 14:33:00 +0100, wrote:
> > > On Thu, 17 Mar 2011 09:24:26 -0400
> > > "R. David Murray" wrote:
> >
On Sun, 20 Mar 2011 00:06:01 -0400, "R. David Murray"
wrote:
> It would have been nice if rebase had refused to run given that
> there were merges, since it clearly doesn't work in that case.
To clarify, that should have read "given that there were merges
*between br
ges (except
for the RFC 4180 one) and made them on 3.1, 3.2, and harmonized default.
So this should all be good now, except for the RFC change. I guess I'll
see about doing that one later.
--
R. David Murray http://www.bitdance.com
___
o you're working with.
And, as I discovered, only if they are on a single branch. Which is
something *none* of the documentation I've read has mentioned. Perhaps
that's because named branches are relatively new?
--
R. David Murray http://www.bitdance.com
before starting my merge dance and am unlikely
to *re*run the regrtest after having to do an hg pull/merge heads,
exactly the same size hole is going to exist in my hg workflow.
--
R. David Murray http://www.bitdance.com
___
Python-Dev mailing l
latform-independence. UNIX won't
> understand that, and I don't think we're gonna be able to convince all
> the kernel developers to implement this simplified shebang.
+1. If one of the points is to be compatible with PEP 394, then
the above seems like a bad
ad the same need to merge to tip as with hg,
and the same lack of enforcing of the running of tests.
--
R. David Murray http://www.bitdance.com
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
On Mon, 21 Mar 2011 18:33:00 +0900, "Stephen J. Turnbull"
wrote:
> R. David Murray writes:
> > On Mon, 21 Mar 2011 14:07:46 +0900, "Stephen J. Turnbull"
> wrote:
> > > No, at best the DVCS workflow forces the developer on a branch to
> > >
On Mon, 21 Mar 2011 15:59:51 +0100, Adrian Buehlmann wrote:
> On 2011-03-21 14:40, R. David Murray wrote:
> > On Mon, 21 Mar 2011 18:33:00 +0900, "Stephen J. Turnbull"
> > wrote:
> >> R. David Murray writes:
> >> > On Mon, 21 Mar 2011 14:0
hell does, while my bash shell doesn't: because I
don't use bash, I installed mercurial without bash-completion.
So: there is completion support for hg update for both bash and zsh.
Not sure about other shells.
--
R. David Murray http://www.bitdance.com
7;t really know (probably a null merge, but you'll
have to figure out the state of your repo first...or you could start
over with a fresh clone).
--
R. David Murray http://www.bitdance.com
___
Python-Dev mailing list
Python-Dev@python.org
to some
> sort of serialization scheme?
Note that svnmerge broke at exactly the same scale point, for exactly the
same reason: every svnmerge touched root properties, thereby effectively
serializing access to the tree. There were lots of curses from people
trying to svnmerge at th
made changes, whereas that safety-belt svn up before
the svn ci doesn't.
--
R. David Murray http://www.bitdance.com
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http:/
from
one or more people with interest in this area, maybe we can get some
people with relevant knowledge onto the development team.
--
R. David Murray http://www.bitdance.com
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.or
orrect solution, otherwise you'll
just run in to the trouble when you try to merge the branch into default.
--
R. David Murray http://www.bitdance.com
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinf
operly, but they are isolated
cases and don't bother me much (mostly a couple older tools that just
don't have good non-ascii support).
> Mind you, I've never managed to get the <-- button working reliably
> either, but to be fair that's insanely complicated too.
No idea
On Sun, 27 Mar 2011 19:46:35 +0100, Jon Ribbens
wrote:
> On Sun, Mar 27, 2011 at 02:21:25PM -0400, R. David Murray wrote:
> > > Mind you, I've never managed to get the <-- button working reliably
> > > either, but to be fair that's insanely complicated
part is debugging the TAL when you make a mistake, but
even that isn't a whole lot worse than any other templating language.
--
R. David Murray http://www.bitdance.com
___
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
les to your personal ignore list See the 'ignore'
entry under 'ui' in the hgrc documentation.
--
R. David Murray http://www.bitdance.com
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo
On Wed, 30 Mar 2011 12:17:05 +1100, Mark Hammond
wrote:
> On 30/03/2011 12:09 PM, R. David Murray wrote:
> > The solution is to add such
> > directories and/or files to your personal ignore list See the 'ignore'
> > entry under 'ui' in the hgrc document
> elegant solution.
Flicker or not, I don't like it myself. I've turned off javascript on
bugs.python.org in my browser, and now it doesn't bother me anymore.
But I don't think that is a good long term solution. Making it optional
based on a setting in the user profile might
indeed redundant, but the sidebar is not really usable here.
I agree with this point. The sidebar list of questions is effectively
useless.
Most FAQ lists start with the long list of questions. I don't see
why this one should be different :)
--
R. David Murray http://www.bitdance.com
On Thu, 31 Mar 2011 23:59:36 +0200, =?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=
wrote:
> Notice that the issue title was always there, in your browser's title
> bar (unless you have a web browser that doesn't display the page title).
I do.
--
R. David Murray http://
On Fri, 01 Apr 2011 08:29:29 +1000, Nick Coghlan wrote:
> On Fri, Apr 1, 2011 at 2:34 AM, R. David Murray wro=
> te:
> > I agree with this point. =A0The sidebar list of questions is effectively
> > useless.
>
> Indeed. If it's simple, I'd actually be inc
On Fri, 01 Apr 2011 12:47:12 +0200, Georg Brandl wrote:
> Am 01.04.2011 01:12, schrieb R. David Murray:
> > On Fri, 01 Apr 2011 08:29:29 +1000, Nick Coghlan wrote:
> >> On Fri, Apr 1, 2011 at 2:34 AM, R. David Murray
> >> wro=
> >> te:
> >> >
e can argue about the semantics when we
discuss individual tests :)
100% branch coverage as measured by coverage.py is one good place to
start for building such a comprehensive test suite. Existing tests
for C versions getting (or newly testing) Python code is another.
Bug reports from alternate
rs. It never occurred to me to change the variable and type c
> without first checking that the variable had changed... :-)
>
> It is however fixed in 2.7.
For the curious:
http://bugs.python.org/issue5215
--
R. David Murray http://www.bitdance.com
_
#x27;t reread the PEP to check.) The
idea is to use the test suite as the check for this, adding tests as
necessary.
--
R. David Murray http://www.bitdance.com
___
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
27;t that distutils2 would help the OP,
but that the OP could help Distutils2 and the community by taking his
use case to the developers and making sure that that use case is
supported before the release of packaging in 3.3.
--
R. David Murray http://www.bitdance.com
l super() is almost certainly deliberate.
Why not? It seems more useful than using it for chaining,
especially given the compiler hack in Python3.
--
R. David Murray http://www.bitdance.com
___
Python-Dev mailing list
Python-Dev@python
> IronPython,
> and Jython to succeed, does the CPython project need to come to a halt? I
> don't
> think many people here really believe that to be the case.
No, I don't think any of these things are aims. But if/once the Python
stdlib is a separate repo, then in *that*
a mailing list for
security related announcements on which only the "security officer" or
"security team" posts announcements, and security related announcements
*only*. Then then the people responsible for security in any context
(a distribution, a
701 - 800 of 1043 matches
Mail list logo
