Jakub Filak

@amosang Good catch. Could you file a new issue, please?

@krzysztof-slowinski You are right. @mamiksik is already working on the support for V4.

We are still working on it but we will get there once.

> 1. I do believe all the information is in @mamiksik 's wiki: - https://github.com/mamiksik/python-pyodata/wiki/OData-V4 - https://github.com/mamiksik/python-pyodata/wiki/What-is-missing%3F > 2. I am sorry but it's hard to tell - I guess...

I am not against it as long as we keep also the possibility to fetch the navigation property using the standard way which allows us to specify HTTP parameters.

@mamiksik I was under the impression that this issue was fixed few months ago. What's the status of error policies? Can we configure policies to ignore this particular warning?

So you want to merge and expect that people know that pypy3 can fail?

You are absolutely right. The current code reads "ABAP Odata annotations" and your service is from SuccessFactors. Honestly, adding support for the SAP attributes to pyodata directly was a bad...

I would create a solo directory for translations and store each language in own file like we do in gettext.

Then we need to create a file per object (in a special directory for translations). Less files, more merge conflicts ... more files, less conflicts. Or not?