a weird thing in the source code comments

[argriffing]

This url in the source code is out of control

http://groups.google.com/groups?hl=en&lr=&threadm=mailman.5090.1098044946.5135.python-list%40python.org&rnum=1&prev=/groups%3Fq%3D__doc__%2Bauthor%253Ajdhunter%2540ace.bsd.uchicago.edu%26hl%3Den%26btnG%3DGoogle%2BSearch

[pelson]

It relates to a problem with python 2.2. I think we are now only supporting 2.6 onwards - so it might be time to refactor this bit of code anyhow.

[pganssle]

If I'm right about what he's referring to, MEP13, if implemented, would replace these get_ and set_ methods with properties anyway.

Either way, though, the URL seems to be dead, and I can't find an archive of the particular message anywhere, so it's not clear that it's doing much in the source code as is.

[WeatherGod]

Link rot sucks. We should double-check for other links that may be more
susceptible to link-rot (although I am surprised at losing a google groups
message).

On Sat, Dec 27, 2014 at 1:17 PM, Paul G. notifications@github.com wrote:

If I'm right about what he's referring to, MEP13
https://github.com/matplotlib/matplotlib/wiki/MEP13, if implemented,
would replace these get_ and set_ methods with properties anyway.

Either way, though, the URL seems to be dead, and I can't find an archive
of the particular message anywhere, so it's not clear that it's doing much
in the source code as is.

—
Reply to this email directly or view it on GitHub
#3948 (comment)
.

[tacaswell]

This https://mail.python.org/pipermail/python-list/2004-October/255696.html may be the discussion in question.

It looks like that url is actually a search query and google has sense changed their internal api...

[WeatherGod]

Might make sense to fix this in PR #3949

On Mon, Dec 29, 2014 at 10:18 PM, Thomas A Caswell <notifications@github.com

wrote:

This
https://mail.python.org/pipermail/python-list/2004-October/255696.html
may be the discussion in question.

It looks like that url is actually a search query and google has sense
changed their internal api...

—
Reply to this email directly or view it on GitHub
#3948 (comment)
.