Closed GoogleCodeExporter closed 9 years ago
Thanks for reporting that this is causing you problems.
You're right that I was never really sure what the "right" thing to do was in
this case. Printing an empty frame *does* seem reasonable. I'll try to do a
0.7.2 release tomorrow which either reverts to the old behaviour, or perhaps
introduces an option which can be used to choose the behaviour for empty
tables, so that people who have particular needs can set it accordingly. I'd
still like to give exactly what to do a little thought...
I'm quite busy IRL at the moment, so there's a chance this might slip of my
radar - if I haven't done the 0.7.2 release in a couple of days, please feel
free to comment on this issue and remind me. I understand you probably want to
see this fixed ASAP if it's wreaking havoc with your unit tests.
Original comment by luke@maurits.id.au
on 1 Apr 2013 at 5:42
I implemented an ugly workaround for the time being (if no rows, add one, then
strip it out using str.splitlines()), so there's no need for hurry on my behalf.
Original comment by mged...@gmail.com
on 1 Apr 2013 at 7:43
I have released 0.7.2 today which fixes this problem.
By default, empty tables will now be printed as empty frames as was the old
behaviour. But by setting "print_empty" to False, the behaviour of returning
an empty string can be chosen instead.
Thanks for your patience on this.
Original comment by luke@maurits.id.au
on 7 Apr 2013 at 2:19
Original issue reported on code.google.com by
mged...@gmail.com
on 29 Mar 2013 at 12:00