From: OceanWolf <jui...@ya...> - 2015-03-10 16:34:09
|
Yes, you have almost got what I want. I know of both line comments in the pull interface, and raising DeprecationWarnings. The problem with the warnings that they only want to get used when you have an alternate in place and want to remove old code soon. The problem here lies in not knowing how long the life-cycle will last for an indeterminate amount of time, such as numpy-1.5 here, or python-2.7. Lots of such items can stack up, and easily get forgotten about, as we see here. On 10/03/15 17:12, Paul Hobson wrote: > You can comment on specific lines of code in the pull request > interface, but that's not what I think you're describing. A better > practice, IMO is to raise a DeprecationWarning when the > soon-to-be-removed code is executed. Then you can just grep for those > and get cracking. > -p > > On Tue, Mar 10, 2015 at 8:51 AM OceanWolf > <jui...@ya... <mailto:jui...@ya...>> > wrote: > > Slightly off-topic, does github allow for one to tag lines/code-blocks > with notes to the future like ``numpy1.5 removal'', similar to > tags for > issues and milestones? This would save us from trawling through the > code looking for comments. If github does not have this feature, > do you > think github would add that as a feature if asked? > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel > Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your > hub for all > things parallel software development, from weekly thought > leadership blogs to > news, videos, case studies, tutorials and more. Take a look and > join the > conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > <mailto:Mat...@li...> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > |