On Sep 25, 2014, at 8:50 AM, Eric Gallager wrote:
> Maybe not new py24-foo or new py25-foo ports, but what about +python24
> or +python25 variants for ordinary ports that have python bindings?
I'm not sure what you're asking. I don't think people are introducing new
variants either. In any case
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
On 23 Sep 2014, at 04:46, Lawrence Velázquez wrote:
> Maintaining old versions of CPython that aren't supported upstream is
> annoying and a poor use of our time, so I'd like to propose
> a maintenance policy. After we chit-chat about it, I'll write something
> up on the wiki (hopefully a little
On Sep 23, 2014, at 3:49 AM, Andrea D'Amore wrote:
> The policy is informally half in place, noone is actually creating new
> py24-foo or py25-bar (or at least I hope soo)
Yup.
Most of it really is just common sense. I just want to formalize it for the
future, so we have something to point to
Brandon Allbery writes:
> On Tue, Sep 23, 2014 at 12:49 AM, Sean Farley wrote:
>
>> I actually have the back story for this from the last PyCon. Suffice to
>> say, it's because of Python 3 screwing up the treatment of unicode
>> strings.
>>
>
> Huh. I'd assumed arm-twisting from Red Hat, possibl
On Tue, Sep 23, 2014 at 12:49 AM, Sean Farley wrote:
> I actually have the back story for this from the last PyCon. Suffice to
> say, it's because of Python 3 screwing up the treatment of unicode
> strings.
>
Huh. I'd assumed arm-twisting from Red Hat, possibly with an education
about enterprise
On Tue, Sep 23, 2014 at 6:49 AM, Sean Farley wrote:
> it's because of Python 3 screwing up the treatment of unicode strings.
It's spelled "improved".
I'm liking py3 insofar.
--
Andrea
___
macports-dev mailing list
macports-dev@lists.macosforge.org
On Tue, Sep 23, 2014 at 4:46 AM, Lawrence Velázquez 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 py
Lawrence Velázquez writes:
> Maintaining old versions of CPython that aren't supported upstream is
> annoying and a poor use of our time, so I'd like to propose
> a maintenance policy. After we chit-chat about it, I'll write something
> up on the wiki (hopefully a little clearer) and inform macpo
Maintaining old versions of CPython that aren't supported upstream is
annoying and a poor use of our time, so I'd like to propose
a maintenance policy. After we chit-chat about it, I'll write something
up on the wiki (hopefully a little clearer) and inform macports-users.
The term "replaced by" si
10 matches
Mail list logo
