On Oct 18, 2014, at 11:21 AM, petr wrote: > > On 18 Oct 2014, at 17:45, Ryan Schmidt wrote: > >> >>> On Oct 18, 2014, at 9:19 AM, p...@macports.org wrote: >>> >>> Revision >>> 126965 >>> Author >>> p...@macports.org >>> Date >>> 2014-10-18 07:19:30 -0700 (Sat, 18 Oct 2014) >>> Log Message >>> >>> py-mssql: update to 2.1.0, remove py24, py25 subport >> >> Perhaps we want to add them to py-graveyard? > > Maybe, was considering this, but I am not really sure. > > This is not really related to the deprecation process.
Yes it is, in that we're in the process of deprecating all python 24 and 25 modules, and other old python versions. > The situation here is rather comparable to what we did earlier when updating > ports and older Python versions were not supported. We did not have a good method for upgrading users to newer supported versions before; now, with py-graveyard, we do, and I think we should use it. > But on the other hand, adding this to py-graveyard should not have any > drawback and might even provide a smoother user experience. > > I understood, that the new subport (here: py27) should be already around when > adding to py-graveyard. So this always needs to be a two step process. But > keeping the unsupported subport(s) around when updating makes no sense. Right? > > Should I add I now? That's my suggestion. _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
