On a related note. What is the recommended procedure for dealing with depreciations? Do we just update all the deprecations and push the changes? This would make the package useless for 0.3 users or is this the recommended procedure.
On Friday, October 16, 2015 at 7:39:05 PM UTC-4, Forrest Curo wrote: > > So what's the easiest way -- given a long, long list of warnings -- to > find out what needs to be changed in a program (It runs, after replacing > calls to 'Base.Graphics' with 'Graphics' -- but the tk button that used to > close the window and exit now doesn't (Ah! I need to remember the default I > changed for those buttons to make that button work the way I wanted! (What > *was > *that?!))) > > and what should now be substituted? > > I mean, I could just follow that list of warnings from the top... but I'd > like to know a reference listing displaced packages & their replacements. >
