On Thursday, August 4, 2016 at 7:03:32 PM UTC-5, Lawrence D’Oliveiro wrote:
> As GvR has said: “we’re all consenting adults here”.
But as we've learned from animal farm, some are more consenting than others.
--
https://mail.python.org/mailman/listinfo/python-list
Op 05-08-16 om 02:03 schreef Lawrence D’Oliveiro:
> On Wednesday, August 3, 2016 at 3:13:01 AM UTC+12, Robin Becker wrote:
>> A reportlab user found he was doing the wrong thing by calling
>> canvas.save repeatedly, our documentation says you should not use Canvas
>> objects after the save method h
On 05/08/2016 01:03, Lawrence D’Oliveiro wrote:
objects after the save method has been used. The user had mixed results :(
As GvR has said: “we’re all consenting adults here”.
In other words, we”re capable of coping with the consequences of our actions.
agreed :)
--
Robin Becker
-
On Wednesday, August 3, 2016 at 3:13:01 AM UTC+12, Robin Becker wrote:
> A reportlab user found he was doing the wrong thing by calling
> canvas.save repeatedly, our documentation says you should not use Canvas
> objects after the save method has been used. The user had mixed results :(
As GvR has
Robin Becker writes:
> A reportlab user found he was doing the wrong thing by calling canvas.save
> repeatedly, our documentation says you should not use Canvas objects after
> the
> save method has been used. The user had mixed results :(
>
> It would be better to make the canvas object compl
On Wed, 3 Aug 2016 01:12 am, Robin Becker wrote:
> A reportlab user found he was doing the wrong thing by calling canvas.save
> repeatedly, our documentation says you should not use Canvas objects after
> the save method has been used. The user had mixed results :(
>
> It would be better to make
On Tuesday, 2 August 2016 16:13:01 UTC+1, Robin Becker wrote:
> A reportlab user found he was doing the wrong thing by calling canvas.save
> repeatedly, our documentation says you should not use Canvas objects after
> the
> save method has been used. The user had mixed results :(
>
> It would
A reportlab user found he was doing the wrong thing by calling canvas.save
repeatedly, our documentation says you should not use Canvas objects after the
save method has been used. The user had mixed results :(
It would be better to make the canvas object completely immutable all the way
down w
