pyglet 1.3.0b1

[Rob]

Hi all,

I am proud to present the first beta version of pyglet 1.3.0. This version should contain all the functionality we want to release for 1.3.0. But we now need _your_ help to test it. Please try it in your projects and inform us of any issues you find.

The easiest way to get this release is using pip:

pip install pyglet==1.3.0b1

I recommend you do this in a virtualenv to not remove the existing version of pyglet on your system.

Release notes: https://bitbucket.org/pyglet/pyglet/raw/928d7bd532ef4be72a45599a77ffcdbcdde7712d/RELEASE_NOTES

Documentation: http://pyglet.readthedocs.io/en/pyglet-1.3-maintenance/

Downloads: https://bitbucket.org/pyglet/pyglet/downloads/

Pypi: https://pypi.python.org/pypi/pyglet/1.3.0b1

Please report issues here: https://bitbucket.org/pyglet/pyglet/issues

Kind regards,

Rob

[Serdar Yegulalp]

Excellent, long-awaited news!

I have a fairly large project that uses Pyglet, so I'll try it as a drop-in replacement and put it through its paces over the next couple of weeks.

[Bruce Smith]

> I recommend you do this in a virtualenv to not remove the existing version of pyglet on your system.

For those of us who rarely use virtualenv, can you show us a short command sequence which would install or update virtualenv, create a new virtualenv, install pyglet 1.3.0b1 in it, and run an existing python program in it (consisting of many python files, some of which do sys.path manipulations to import python files from non-child directories)? (In my case I normally use python 2.7 and run this by typing something like "python main.py".)

(I'd be happy to test the new pyglet release this way, but I keep putting off the needed googling to answer that virtualenv question myself, and I'm guessing someone here just knows the answer.)

- Bruce Smith

--
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 pyglet-users+unsubscribe@googlegroups.com.
To post to this group, send email to pyglet...@googlegroups.com.
Visit this group at https://groups.google.com/group/pyglet-users.
For more options, visit https://groups.google.com/d/optout.

[Benjamin Moran]

Hi Bruce,

If you're on Linux, this should do it:

python -m venv  pygletvenv
source pygletvenv/bin/activate
pip install pyglet==1.3.0b1

After you've called bin/activate, you should see your bash shell indicate that you're in a venv. Any programs you run from this point will use the python interpreter and libraries that you've installed while inside this virtualenv.  When you're done, simply type "deactivate" to exit from the virtual environment.

As a quick test, simply type "python", then "import pyglet", and check "pyglet.version".

On Saturday, May 13, 2017 at 12:56:36 PM UTC+9, Bruce Smith wrote:

> I recommend you do this in a virtualenv to not remove the existing version of pyglet on your system.

For those of us who rarely use virtualenv, can you show us a short command sequence which would install or update virtualenv, create a new virtualenv, install pyglet 1.3.0b1 in it, and run an existing python program in it (consisting of many python files, some of which do sys.path manipulations to import python files from non-child directories)? (In my case I normally use python 2.7 and run this by typing something like "python main.py".)

(I'd be happy to test the new pyglet release this way, but I keep putting off the needed googling to answer that virtualenv question myself, and I'm guessing someone here just knows the answer.)

- Bruce Smith

On Sat, May 6, 2017 at 11:36 AM, Rob <silves...@gmail.com> wrote:

Hi all,

I am proud to present the first beta version of pyglet 1.3.0. This version should contain all the functionality we want to release for 1.3.0. But we now need _your_ help to test it. Please try it in your projects and inform us of any issues you find.

The easiest way to get this release is using pip:

pip install pyglet==1.3.0b1

I recommend you do this in a virtualenv to not remove the existing version of pyglet on your system.

Release notes: https://bitbucket.org/pyglet/pyglet/raw/928d7bd532ef4be72a45599a77ffcdbcdde7712d/RELEASE_NOTES

Documentation: http://pyglet.readthedocs.io/en/pyglet-1.3-maintenance/

Downloads: https://bitbucket.org/pyglet/pyglet/downloads/

Pypi: https://pypi.python.org/pypi/pyglet/1.3.0b1

Please report issues here: https://bitbucket.org/pyglet/pyglet/issues

Kind regards,

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 pyglet-users...@googlegroups.com.

[Rob van der Most]

Also these instructions should help for all platforms:

http://pyglet.readthedocs.io/en/pyglet-1.3-maintenance/internal/virtualenv.html

Rob

To unsubscribe from this group and stop receiving emails from it, send an email to pyglet-users+unsubscribe@googlegroups.com.

[Bruce Smith]

Hi Rob,

Thanks! Your commands did not quite work, but they came close enough that I found the motivation to do the much-reduced "incremental googling" needed to make them work.

I'm on a Mac (close enough to linux) and normally use tcsh (for this test, I switched to bash). To make your commands work, I only had to:

- first do 'sudo pip install virtualenv --upgrade'  (I don't know if this was necessary, but my prior version was old)

- replace 'python -m venv' with 'virtualenv' in your suggested commands -- without this, it failed with "No module named venv" (even after upgrading virtualenv). (I never upgraded pip -- could that be the problem? Another possibility -- my python 2.7 comes from ActiveState (ActivePython 2.7.8.10), not python.org.)

Anyway, after that, "python" was using the new pyglet, and the first pyglet program I tried worked. I will keep using the new pyglet and report any problems. (BTW, thanks very much for all your work in producing this upgrade.)

Do you happen to know whether .pyc files should be compatible between virtualenvs (assuming the same python executable produced them, not counting virtualenv's copy as being different from the one it was based on), or should I remove all .pyc files when switching virtualenvs, as a precaution? (I know that, in theory, .pyc files are supposed to contain version information that makes it unnecessary to ever remove them, but in practice, I have had crashes from not removing them when switching python executables.)

- Bruce Smith

[Stu.Axon]

Probably a bit late, but in case anyone finds this in future:

venv is python3, while virtualenv is python2 (and sometimes 3), it can get confusing.

[Benjamin Moran]

Not too late :)
I'll see if I can clarify this in the documentation.
Thanks for the feedback.

-Ben

[Benjamin Moran]

Hey Stu,

I've started to update the docs a bit to illustrate the different libraries. You can have a look here:
http://pyglet-test.readthedocs.io/en/latest/internal/virtualenv.html

On Monday, August 14, 2017 at 9:12:46 AM UTC+9, Stu.Axon wrote:

[Stu.Axon]

Yup, looks good to me :)

[Benjamin Moran]

Great! I'll get that merged in.