python-hyper
add a dependency on incremental for deprecation
Since there's a bunch of stuff I am proposing removing ( #24 #25 #26 ) we should probably have a way of emitting some warnings and generally tracking when things need to be removed. https://pypi.python.org/pypi/eventually has some functionality that can do that. (This issue doesn't really stand on its own; we don't need it until we've got agreement & implementation on one of those other issues.)
Hmm, I've certainly heard of eventually here and there, but I've never used it. Also, it's apparently not announced yet nor does the PyPI link to a codebase. I guess I'm not sold?
Besides, I also don't feel like the APIs being discussed have been around long enough to merit that much pomp and circumstance. In some cases (e.g., a couple args to replace), they never even existed. But we'll talk further in the respective threads.
Hmm, I've certainly heard of eventually here and there, but I've never used it. Also, it's apparently not announced yet nor does the PyPI link to a codebase. I guess I'm not sold?
Oh, sorry. Maybe we decided to put this functionality into incremental instead?
Presumably this depends on incremental inheriting the appropriate functionality; it's the stuff that currently lives in twisted.python.deprecate.
Ah, yes, I've used incremental. I could see needing this for, e.g., replacing userinfo with separate username and password fields.