Re: Issue 241 in pyglet: Document doesn't allow replacement of text

[codesite...@google.com]

Comment #6 on issue 241 by euccastro: Document doesn't allow replacement of
text
http://code.google.com/p/pyglet/issues/detail?id=241

As others have said, this is not really fixed. See

http://code.google.com/p/pyglet/issues/detail?id=471

(Sorry about the duplication. When I searched for existing issues I left
the drop
down menu at "Open Issues" so this one didn't show up.)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[codesite...@google.com]

Comment #7 on issue 241 by oresmus: Document doesn't allow replacement of
text
http://code.google.com/p/pyglet/issues/detail?id=241

I think there are several different issues here, some of which are still
open; see
also related issue 429. I'm going to try to sort this out, as follows.

* There is the original bug Richard reported in this issue (without a
specific test
case). Presumably Alex fixed *something* with r1872, but I don't know how
to find
that revision now that we've switched to mercurial, nor which svn
branch(es) it was
fixed in. The reported original traceback is extremely similar to some that
still
occur with open bugs (eg issue 471). So my best guess is that there was a
more
general bug (e.g. maybe it didn't depend on having any styled text), Alex
fixed that,
but the same traceback still occurs in other cases.

I think it's simplest to consider that unknown original bug (i.e. this
issue) to be
different than the newer bugs (since it was fixed and they are not).
Therefore, this
issue can remain closed, and the subsequent comments can be treated as
reporting
different bugs, some of which are already reported in different issues.

Specifically, that means open issue 471 is *not* a duplicate of this issue,
even
though it has a similar traceback.

* Both code samples in comment 4, and the first one in comment 5, still
fail for me
in the current hg head, i.e. pyglet 1.2dev, on Mac OS 10.6.3, using Python
2.6.2 installed from python.org. (FYI, I have no problems running that
combination of
pyglet, python, and Mac OS in general, in spite of reported issues with
similar
combinations but pyglet 1.1.3, e.g. in issue 438.) I will consider them to
be part of
issue 471. (Two of them -- the ones with a non-empty document -- have almost
identical tracebacks, and the other one has a similar traceback, so they
may still
turn out to involve two different bugs.)

I will refer to this from issue 471, so that whoever fixes that can make
sure this
also fixes the code samples here in comments 4 and 5, and if not, open
separate bug
reports for them.

* I didn't retry the Python crash reported in comment 5 lately. If I or
anyone else
retries that and it still crashes or fails, it should be reported in its
own new issue.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--

You received this message because you are subscribed to the Google Groups "pyglet-issues" group.
To post to this group, send email to pyglet...@googlegroups.com.
To unsubscribe from this group, send email to pyglet-issue...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/pyglet-issues?hl=en.