On Thu, 11 Aug 2016, Lawrence Velázquez wrote:
> > On Aug 11, 2016, at 3:40 PM, Fred Wright <f...@fwright.net> wrote: > > > > Well, leaving something alone that's working just fine is hardly much > > of a maintenance burden. > > As Josh noted, this approach is fine for CPython itself, but less so > for modules. As they work to keep their modules up to date, maintainers > can hardly be expected to support subports for Python versions that > don't build on recent OSes (although they are certainly welcome to if > they wish). But often the subports work fine as well. For example, here I have local versions of seven py-xxx ports just to expand the version lists. In five of the cases, expanding the version lists "just worked". The other two ports each had a set of version-specific files (for no obvious reason, given the content) which just needed to be trivially and obviously expanded for the added versions. Fred Wright _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
