Maybe not new py24-foo or new py25-foo ports, but what about +python24 or +python25 variants for ordinary ports that have python bindings? For example, this isn't the port itself, but from reading the upstream gdb mailing lists, it looks like gdb upstream actually extended their support for python backwards to python24 with their most recent release this summer (7.8), whereas before they had only supported back to python26...
On 9/23/14, Andrea D'Amore <and.dam...@macports.org> wrote: > On Tue, Sep 23, 2014 at 4:46 AM, Lawrence Velázquez <lar...@macports.org> > wrote: > >> ====== POLICY ====== >> […] > > The policy is informally half in place, noone is actually creating new > py24-foo or py25-bar (or at least I hope soo), that said > I'm glad to see old py* ports being phased out. > > This could be handled by the python** portgroups that are already in > place after defining stable-version (or latest-stable) variable in the > main portgroup. > > -- > Andrea > _______________________________________________ > macports-dev mailing list > macports-dev@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-dev > _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
