For comparison, the next release of Panda3d (according to one of their main
developers, writing on a public forum) is planning to retain support for
Python 2.6 (as opposed to 2.7) since they still have users on Mac OS X
before 10.7.

In general, I think "developers" tend to have newer hardware, OSes, etc,
than "users" do, and also find upgrading (when forced to do so) less
difficult, so they tend to underestimate demand for support for older
environments. (In this example I'm applying this to both Carbon and Python
2.x.)

So just as I said for Carbon in another thread, I'd strongly caution
against actually dropping support for Python 2.x, at least not before
confirming a belief that hardly anyone cares. Having printed deprecation
warnings for at least one major version (which could be 1.2) might be one
way to find out how many people care.

On the other hand, pyglet is so stable (its "scope" is in theory perfectly
stable) that the only reason it needs new releases is bugfixes and to keep
up with evolving platforms, so this lessens the argument I'm making. So if
you just want to say something like "1.2 is for the past, 1.3 is for the
future", and document it well, it would be hard to object. (Especially if
it's still practical to accept bugfixes for the 1.2 branch even after 1.3
is released.)

As for a "Python 3 default and 3to2 approach", as long as it worked
smoothly in practice for users of Python 2.x, I don't see a problem with
it, so I'd say "whatever the active developers prefer". (I have never tried
it and have no idea whether it could in fact work smoothly.)

- Bruce Smith


On Sun, Jan 25, 2015 at 11:52 PM, Rob <[email protected]> wrote:

> I think that is more tricky. Lots of people are still relying on Python
> 2.x. So removing support for that will make a lot of people unhappy. We
> could however go for the Python 3 default and 3to2 approach. At least give
> the right example ;-).
>
> Rob
>
> Op maandag 26 januari 2015 04:44:36 UTC+1 schreef Leif Theden:
>
>> That's a great idea!  I wonder if anyone has already done that?  :p
>>
>> On Sunday, January 25, 2015 at 8:35:52 PM UTC-6, Richard Jones wrote:
>>>
>>> I'd be tempted to say any references to Python 2.x should also be
>>> removed ;)
>>>
>>> On Mon Jan 26 2015 at 1:13:44 PM Leif Theden <[email protected]> wrote:
>>>
>>>> All references to osx carbon should be removed.  Apple has not
>>>> supported it for years.
>>>>
>>>>
>>>>
>>>>
>>>> On Sunday, January 25, 2015 at 5:33:40 AM UTC-6, Rob wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>> I just created a release candidate for 1.2. The files are available on
>>>>> BitBucket: https://bitbucket.org/pyglet/pyglet/downloads
>>>>>
>>>>> Release notes are available here: https://bitbucket.org/py
>>>>> glet/pyglet/src/c42a9d8c1c759428299b2d326cdc91a8acee825c/
>>>>> RELEASE_NOTES?at=pyglet-1.2-rc1
>>>>>
>>>>> I will also try to create an .msi. However I do not have a Mac, so I
>>>>> cannot roll a package for OSX.
>>>>>
>>>>> I will start testing this on Linux and Windows. Can someone try it on
>>>>> OSX?
>>>>>
>>>>> Rob
>>>>>
>>>>  --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "pyglet-users" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to [email protected].
>>>> To post to this group, send email to [email protected].
>>>> Visit this group at http://groups.google.com/group/pyglet-users.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>  --
> You received this message because you are subscribed to the Google Groups
> "pyglet-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/pyglet-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"pyglet-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pyglet-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to