A traceback would help if I had one. In the past once I ran
"dabo.ui.loadUI('wx')" and all the imports worked like:
from dabo.ui import dKeys as dKeys
from dabo.lib import dates
I can get around the above imports but I can't get around:
class MainForm(dabo.ui.dForm)
The app just can't find dForm. So I guess you might call that a traceback.
I believe the "dabo.ui.loadUI('wx')" created the way to allow the
"dabo.ui.dForm" to work but I haven't found a way to make it work.
BTW I was able to get dGrid to work under python 3.6 but not
completely. Using the last checkbox (can't recall the label) in the
test causes the app to crash. When I say crash I mean crash without a
traceback - only a message dialog from python stating that python
crashed appears. I did get many other dfileName.py files to run and I
can open a blank Dabo frame/window with a connection to postgres. I'm
still getting some very strange error/warnings from dGrid. It's hard
to follow the code. I'm sure it has something to do with the supporting
stuff Dabo provides.
I have also been removing six stuff. If I'm to run Dabo (3?) it might
as well be without the stuff to support python 2.
I've always enjoyed working with Dabo and maybe I can again do so on a
new project using python 3 :-).
Johnf
On 06/02/2017 09:49 AM, Edward Leafe wrote:
On Jun 2, 2017, at 2:09 AM, john <[email protected]> wrote:
- any thoughts on how to get it to work correctly with python 3.6?
A traceback would help. Did it output one?
-- Ed Leafe
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message:
http://leafe.com/archives/byMID/[email protected]
