On 2017-04-17 16:30-0700 Alan W. Irwin wrote:
> I feel it is important to get back to Python 2 PostScript difference
> perfection and to also achieve that perfection for Python 3.
I now (commit 9185cce) have achieved perfect PostScript difference
reports for both Python 2 and Python 3. I had nev
On 2017-04-17 16:30-0700 Alan W. Irwin wrote:
> [T]here are now PostScript consistency issues _both_ for Python 2 and
> Python 3 results that were not there before for Python 2 before your
> push.
>
> python (2)
> Missing examples:
> Differing graphical output : 33
> Missing st
On 2017-04-16 16:55-0400 Hazen Babcock wrote:
> On 02/21/2017 09:26 PM, Alan W. Irwin wrote:
>>
>> I have now been in contact with the OP, Barry Warsaw of python.org, of
>> that thread who was quite helpful. For example, Barry told me that
>> Python is designed so it is frankly impossible for
>>
On 02/21/2017 09:26 PM, Alan W. Irwin wrote:
>
> I have now been in contact with the OP, Barry Warsaw of python.org, of
> that thread who was quite helpful. For example, Barry told me that
> Python is designed so it is frankly impossible for
>
> import Plframe
> from Plframe import *
>
> to race (
On 2017-02-21 11:01-0800 Alan W. Irwin wrote:
> Yesterday for the second time in two months an interactive
> comprehensive test failed with a "ValueError: bad marshal data
> (unknown type code)" error for bindings/python/Plframe.py.
[ These errors were so common]
> that the python developers l
Yesterday for the second time in two months an interactive
comprehensive test failed with a "ValueError: bad marshal data
(unknown type code)" error for bindings/python/Plframe.py. This is a
rather common error with python and typically means the associated
*.pyc that is generated by python has be
