Problem on Windows/PyQt5.8.2, trying master tree (since Qt5 merge)

[stonebig]

launching via

vitables -v 2 -l "C:\WinPython\basedir36\buildQt5\winpython-64bit-3.6.x.1\notebooks\vit.log"

I fall on this error:

2017-04-30 12:49:27,400 - vitables - ERROR -   File "C:\WinPython\basedir36\buildQt5\winpython-64bit-3.6.x.1\python-3.6.1.amd64\Scripts\vitables-script.pyw", line 11, in <module>
    load_entry_point('ViTables==2.2.1.dev0', 'gui_scripts', 'vitables')()
  File "C:\WinPython\basedir36\buildQt5\winpython-64bit-3.6.x.1\python-3.6.1.amd64\lib\site-packages\vitables-2.2.1.dev0-py3.6.egg\vitables\start.py", line 180, in gui
    vtapp = VTApp(mode=args.mode, dblist=args.dblist, h5files=args.h5file)
  File "C:\WinPython\basedir36\buildQt5\winpython-64bit-3.6.x.1\python-3.6.1.amd64\lib\site-packages\vitables-2.2.1.dev0-py3.6.egg\vitables\vtapp.py", line 132, in __init__
    self.gui = vtgui.VTGUI(self, vtconfig.getVersion())
  File "C:\WinPython\basedir36\buildQt5\winpython-64bit-3.6.x.1\python-3.6.1.amd64\lib\site-packages\vitables-2.2.1.dev0-py3.6.egg\vitables\vtgui.py", line 79, in __init__
    self.setup(vtapp)
  File "C:\WinPython\basedir36\buildQt5\winpython-64bit-3.6.x.1\python-3.6.1.amd64\lib\site-packages\vitables-2.2.1.dev0-py3.6.egg\vitables\vtgui.py", line 87, in setup
    self.dbs_tree_model =  dbstreemodel.DBsTreeModel(self, vtapp)
  File "C:\WinPython\basedir36\buildQt5\winpython-64bit-3.6.x.1\python-3.6.1.amd64\lib\site-packages\vitables-2.2.1.dev0-py3.6.egg\vitables\h5db\dbstreemodel.py", line 102, in __init__
    self.tmp_dbdoc = self.__createTempDB()
  File "C:\WinPython\basedir36\buildQt5\winpython-64bit-3.6.x.1\python-3.6.1.amd64\lib\site-packages\vitables-2.2.1.dev0-py3.6.egg\vitables\h5db\dbstreemodel.py", line 324, in __createTempDB
    db_doc = self.createDBDoc(self.tmp_filepath, True)
  File "C:\WinPython\basedir36\buildQt5\winpython-64bit-3.6.x.1\python-3.6.1.amd64\lib\site-packages\vitables-2.2.1.dev0-py3.6.egg\vitables\h5db\dbstreemodel.py", line 304, in createDBDoc
    self.insertRows(0, 1)
  File "C:\WinPython\basedir36\buildQt5\winpython-64bit-3.6.x.1\python-3.6.1.amd64\lib\site-packages\vitables-2.2.1.dev0-py3.6.egg\vitables\h5db\dbstreemodel.py", line 1027, in insertRows
    top_left = self.index(first, 0, parent)
  File "C:\WinPython\basedir36\buildQt5\winpython-64bit-3.6.x.1\python-3.6.1.amd64\lib\site-packages\vitables-2.2.1.dev0-py3.6.egg\vitables\h5db\dbstreemodel.py", line 915, in index
    return self.create_index(row, column, node)
'DBsTreeModel' object has no attribute 'create_index'

[stonebig]

maybe I miss a default/previous/empty hdf5 database ? I'm using pytables-3.4.2

[stonebig]

I see no create_index function in DBsTreeModel class . shouldn't this apply on a column ?

[stonebig]

if I make the line inoperant the gui opens :

if self.hasIndex(row, column, parent) and 1 == 2:

and I have a strange message:

ViTables 2.1
Copyright (c) 2008-2013 Vicent Mas.
All rights reserved.
2017-04-30 14:56:21,526 - vitables.h5db.dbstreemodel - ERROR - Opening failed: file C:\WinPython\basedir36\buildQt5\winpython-64bit-3.6.x.1\notebooks\docs\2 cannot be found.

then if I activate the csv plugin and restart and try to import a csv file:

  File "C:\WinPython\basedir36\buildQt5\winpython-64bit-3.6.x.1\python-3.6.1.amd64\lib\site-packages\vitables-2.2.1.dev0-py3.6.egg\vitables\plugins\csv\import_csv.py", line 627, in csv2Table
    (nrows, descr, has_header) = tableInfo(input_handler)
TypeError: a bytes-like object is required, not 'str'

[stonebig]

the "2' error seems to com from command line interpretor error on "-v 2". the gui seems to "work" but any selection of ".h5" table doesn't display anything.

[ankostis]

Thank you @stonebig for the interest, it is really a nice program.
I will take a look at the problem, but I'm not promising results, it's the first time I programmed in Qt5.

[ankostis]

Fixed by #64 PR.

[ankostis]

@uvemas do you think that current-master is ready for a PyPi release?

@stonebig may prefer a stable "wheel" to work with.

[uvemas]

As I said in other thread I have not tested the current-master in depth. So I prefer to wait before doing a PyPi/wheel/anything release.