pkgsrc/devel/py-deprecation/distinfo

$NetBSD: distinfo,v 1.9 2018/10/07 07:16:55 adam Exp $

SHA1 (deprecation-2.0.6.tar.gz) = 8c788584538c2dbc2ade5573c61c5c438cdec0b2
RMD160 (deprecation-2.0.6.tar.gz) = 682ac715c3f791c7227a39c32b63c2387e370166
SHA512 (deprecation-2.0.6.tar.gz) = 69dcf5e07cfc1c746564e03063088cce65690e2b34cffe327d59edad24f00d23cf9904089ab9ff5e67dce2b6b02ed617e53959be4a907074440ddb778576aa2f
Size (deprecation-2.0.6.tar.gz) = 13381 bytes
py-deprecation: updated to 2.0.6 2.0.6: Unknown changes 2018-10-07 09:16:55 +02:00			$NetBSD: distinfo,v 1.9 2018/10/07 07:16:55 adam Exp $
py-deprecation: added version 1.0.1 The deprecation library provides a deprecated decorator and a fail_if_not_removed decorator for your tests. Together, the two enable the automation of several things: 1. The docstring of a deprecated method gets the deprecation details appended to the end of it. If you generate your API docs direct from your source, you don't need to worry about writing your own notification. You also don't need to worry about forgetting to write it. It's done for you. 2. Rather than having code live on forever because you only deprecated it but never actually moved on from it, you can have your tests tell you when it's time to remove the code. The @deprecated decorator can be told when it's time to entirely remove the code, which causes @fail_if_not_removed to raise an AssertionError, causing either your unittest or py.test tests to fail. 2017-12-31 19:47:08 +01:00
py-deprecation: updated to 2.0.6 2.0.6: Unknown changes 2018-10-07 09:16:55 +02:00			`SHA1 (deprecation-2.0.6.tar.gz) = 8c788584538c2dbc2ade5573c61c5c438cdec0b2`
			`RMD160 (deprecation-2.0.6.tar.gz) = 682ac715c3f791c7227a39c32b63c2387e370166`
			`SHA512 (deprecation-2.0.6.tar.gz) = 69dcf5e07cfc1c746564e03063088cce65690e2b34cffe327d59edad24f00d23cf9904089ab9ff5e67dce2b6b02ed617e53959be4a907074440ddb778576aa2f`
			`Size (deprecation-2.0.6.tar.gz) = 13381 bytes`