QCanDbcFileParse load error

SGaist

@jsulm said in QCanDbcFileParse load error:

@SGaist As far as I can see OP is passing a path to the file

Indeed, I misread the reading/printing and parse call !

@dhagrow, @JonB has a point with regard to UTF-8.

Also, on which OS are you seeing this issue ?

JonB

@SGaist said in QCanDbcFileParse load error:

@dhagrow, @JonB has a point with regard to UTF-8.

Except that error "no such file or directory" does not sound like that, does sound like it's not finding the file. Or a strange message.

SGaist

@JonB said in QCanDbcFileParse load error:

@SGaist said in QCanDbcFileParse load error:

@dhagrow, @JonB has a point with regard to UTF-8.

Except that error "no such file or directory" does not sound like that, does sound like it's not finding the file. Or a strange message.

Indeed, I was just adding more weight with regard to using parseData which was related to my original question about it although it was mainly because I misread the code sample.

dhagrow

QCanDbcFileParser.parseData() does indeed work! Thanks for pointing that out, I hadn't noticed that method. I'm not sure why the encoding would matter. The contents are ASCII, which should be decoded by UTF-8 with no problem.

Nothing obvious strikes me from the source here, but I guess QString is not included in PySide, so I can't easily check.

It does seem like there should be a better error there, but this solves my immediate problem, and hopefully helps anyone else that runs into it. For the record, I'm on Linux. Thanks again!

JonB

@dhagrow
Yes, parseData() will work, the question is why parser.parse(dbc_file) does not seem to open the file from its name. Just try making dbc_file be the correct full path to the file (not just plain "dbc_file") and check whether that makes a difference?

dhagrow

I get this error instead when I pass in a full path, or even when I use any slash, e.g. ./test.dbc.

QCanDbcFileParser.parse: file to open is a directory

JonB

@dhagrow
Well that's very odd if it's a file and is reported as an open directory failure.
And also odd but maybe significant if the path alters message from "No such file or directory" to "file to open is a directory".

dhagrow

I think I found the problem. I noticed that there's an overload for QCanDbcFileParser.parse that takes a QStringList. It turns out that it works if I pass in ['test.dbc']! I then tried ['t'] and ['.'] and get the same errors I was getting above. It seems PySide is wrapping the overloaded method.

JonB

@dhagrow
But I thought you started from passing a sting, like "dbc_file". That should match parse(fileName) where fileName – str. I don't know exactly what you tried? Where did you get dbc_file varibale value from? Be careful of you prompted the user for it with QFileDialog.getOpenFileName(), that returns a list, not just the filename.

I don't know whether you are now saying you are sorted or not.

dhagrow

Yes, I am sorted. The QCanDbcFileParser.parseData option was all I needed, but I see that I can also use QCanDbcFileParser.parse if I pass in the file name in a list.

"dbc_file" came from a command-line argument, so effectively I was making the call like: parser.parse("test.dbc"). That appears to treat the string like a list, so with test.dbc it would try to open t, and with ./test.dbc it would try ., both of which align with the errors I was seeing. I now see that I can make the call like: parser.parse(["test.dbc"]), which works.

Basically, what I am saying is that PySide is not calling QCanDbcFileParser::parse(QString). It is actually calling QCanDbcFileParser::parse(QStringList).

JonB

@dhagrow Fine for a workaround, but if what you say is true that would apparently be a bug in PySide.

SGaist

I agree with @JonB. A Python string shares some interfaces with the list class however it should not trigger that issue. Something is wrong with the binding. You should open a ticket on the bug report system.

dhagrow

Issue created: https://bugreports.qt.io/browse/PYSIDE-3017