[Baypiggies] Unusual unit test behavior on OSX

[Nanshu Chen]

Add sys.stdout.flush() after your print, or replace print with sys.stderr.write.



On Tue, Oct 28, 2014 at 9:34 PM, Tony Cappellini <cappy2112 at gmail.com> wrote:
>  Hello Everyone,
>
>
> When I ran this unit test that I wrote
>
> http://pastebin.com/YxZH4RHR
>
> I'm seeing some very unusual output that I can't explain.
>
> This is the output.
>
> Record #  1, ;180000FFEEDDCCBBAA0099887766554433221122334455667788990AFC
> Record #  2, ;180218778E4017203C02A20C8E4217A2318E4017203C02A20E8E420717
> .
> ----------------------------------------------------------------------
> Ran 1 test in 0.000s
>
> OK
> Record #  3, ;180230EA65ED65EE85E9A204B5E995EACA10F938E999B0E8A5EB290FE8
>
>
> I only have one test method defined at the moment.
> It looks like two iterations are occurring as expected,
> and the last occurs much later.
>
> Why do all three iterations not happen before the unit test framework
> displays "Ran 1 test in 0.000s" ?
>
> Thanks
>
>
> _______________________________________________
> Baypiggies mailing list
> Baypiggies at python.org
> To change your subscription options or unsubscribe:
> https://mail.python.org/mailman/listinfo/baypiggies