On Friday, March 25, 2022 at 11:14:07 PM UTC-7 Rahul wrote: > yes I used some things like *trunc *or *ceil *to fix it however the error > persists on the same line. Pretty weird. Also used what was suggested like > // > but did not work for me. I want to get this fixed soon. However, > If its not possible to fix it "quickly" perhaps someone can suggest me > some plugin to manage fields in the layout for proper UI orientation. > > All suggestions are welcome > > Regards, > *Rahul* > >
Have you examined the type of structured_fields and it's components at the time of the exception? I would add some debug prints just before the for statement. /dps On Thursday, March 24, 2022 at 4:51:46 PM UTC+5:30 snide...@gmail.com wrote: > >> On Thursday, March 24, 2022 at 3:21:01 AM UTC-7 Massimiliano wrote: >> >>> This could be one problem: >>> >>> for i in range((max_row_lines - extra_colspan) / colspan): >>> >>> there are many of this. >>> >>> *range* take an integer, but a division in python3 return a float... >>> >>> >> Interesting, but why doesn't the exception occur in the quoted line with >> the range statement? >> >> The stack trace suggests it occurs after the for loop completes. >> >> (I' also dizzy from the number of places where self.structured fields get >> redone by enumerating itself) >> >> /dps >> >> -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/web2py/66548933-081a-4894-9a69-b6e38a58dfe6n%40googlegroups.com.
