Użytkownik Ed Leafe napisał: > There have been a lot of reports of problems with Dabo grids and Python > 2.7; unfortunately, > the errors aren't in the code, so there is no traceback, just the segfault. > I ran a bunch of debugging to locate what part of the code was causing it, > and it led me to the repeated calls to _getDaboVisibleCols(). > Eliminating those calls got rid of the segfault on my machine. And since > there is no need > to constantly re-calculate which columns are visible, I switched the logic > to only calculating > them when columns may have changed.
This is the right move but deferring it, isn't I think. I had plenty of strange SystemError exceptions with Dabo and Python 2.7. They are gone when I removed autosuper reference from dObject and switched all super calls to use super built-in function instead. Maybe you will try this? -- Regards Jacek Kałucki _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[email protected]
