Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#5768 task closed fixed (fixed)

Remove deprecated

Reported by: Thijs Triemstra Owned by: spiv
Priority: low Milestone:
Component: web Keywords:
Cc: Thijs Triemstra, jknight Branch: branches/remove-google-5768
branch-diff, diff-cov, branch-cov, buildbot
Author: thijs

Description was deprecated in Twisted 11.1 (#5209) and can be removed (inc. the sample).

Attachments (1)

google-5678.patch (5.5 KB) - added by Thijs Triemstra 5 years ago.

Download all attachments as: .zip

Change History (8)

comment:1 Changed 5 years ago by DefaultCC Plugin

Cc: jknight added

Changed 5 years ago by Thijs Triemstra

Attachment: google-5678.patch added

comment:2 Changed 5 years ago by Thijs Triemstra

Author: thijs
Keywords: review added

comment:3 Changed 5 years ago by spiv

Owner: set to spiv

comment:4 Changed 5 years ago by spiv

Author: thijsthijs, spiv
Branch: branches/remove-google-5768

(In [34792]) Branch to remove-google-5768

comment:5 Changed 5 years ago by spiv

Author: thijs, spivthijs
Keywords: review removed

Tests pass locally, and it's hard to object to deleting code! I don't have a single nitpick to make.

Assuming buildbot likes this I'll submit it. Thank you!

comment:6 Changed 5 years ago by spiv

Resolution: fixed
Status: newclosed

(In [34796]) Merge remove-google-5768: Remove the deprecated module.

Author: thijs Reviewer: spiv Fixes: #5768

Removes, which was deprecated in Twisted 11.1, and associated documentation.

comment:7 Changed 5 years ago by Glyph

Hello eager deprecators (especially Thijs):

In this case I don't object to the removal, because the code we're talking about here can arguably be said to violate Google's terms of service and we should never have shipped it in the first place. (You should be using the google custom search API if you want to automate things, which this module never supported.)

However, tickets like this should be worded so as to explain that the code should be removed for a reason (such as "maybe it violates Google's terms of service"). The fact that code can be removed does not necessarily mean that it should be. Deprecated code should be removed for a specific reason, when it becomes an unreasonable maintenance burden, or if its presence is for some reason confusing or problematic.

Generally, we should hang on to deprecated functionality unless it starts to cause us problems and there is a reason to remove it; doing otherwise is by definition breaking people's programs for no reason.

So, again, no problem with this specific ticket (there is a great reason to remove this code, it just wasn't clearly described), but I am concerned over the general pattern of removing things as soon as we possibly can according to policy. In the future, let's start with a description of why we want to remove it.



Note: See TracTickets for help on using tickets.