deprecate twisted.enterprise.util

[indigo]

safe() doesn't actually always make things safe. quote() is horribly misguided in it's attempt to add quotes to some things and not others. All the other components of this module seem to be parts of other deprecated modules. Also, DBAs might burst in flames if they look at the module closely, which is a huge liability.

[glyph]

Pretty much everything in twisted.enterprise (except adbapi) should have large, aggressive warnings in module docstrings explaining they are deprecated, and not deprecated in favor of anything, just nobody should use them ever. Every function in util should, similarly, emit a deprecation warning if you were to call it.

Would you care to contribute a patch which does this?

[exarkun]

(In [22503]) Branching to 'deprecated-enterprise-3022'

[therve]

• test_entreprise prints a warning about util when run, this warning should be removed.
• test_safe and test_getKeyColumn should probably named test_safeDeprecation and test_getKeyColumnDeprecation
• 2.6.0 could be replaced with 8.0.0, unless I miss something.
• the warning in util show that the deprecation API is not yet complete. Maybe we could open a ticket for a 'deprecate module' facility.

[exarkun]

I renamed the test methods. For the rest, here are my thoughts:

• twisted.enterprise.util, the module, is deprecated, so there should be a deprecation emitted when it is imported. In some future release, we'll delete the whole file, so code which imports it (even if it doesn't use anything from it) will break, so there should be a warning. I dunno what to do about the warning being emitted by the test suite. It's a problem that shows up in a number of places in Twisted.
• 2.6.0 could be replaced with 8.0.0, but plenty of other places in Twisted say 2.6.0 now. Since the release person will have to update some of these numbers anyway, I don't think it's a big deal if new changes use 2.6.0 as well.
• Sounds like a good thing, though I can't think of any way it could work at the moment.

[dreid]

I agree about the warning in util.py, but I also don't know how it should work so I don't think it should hold up this ticket.

I do feel like the _unreleasedVersion and _unreleasedDeprecation are a little wonky, but I can't think of a better way to do it. (A module that just holds deprecation functions for twisted versions perhaps?... I don't know.)

Go ahead and merge both of these issues are for the deprecation framework and shouldn't delay deprecation of something as horrendous as t.e.util.

[exarkun]

(In [22677]) Merge deprecated-enterprise-3022

Author: exarkun Reviewer: therve, dreid Fixes #3022 Refs #3040

Deprecate twisted.enterprise.util and everything in it.