Petr Hanák

Hi @hsajib-jsf no sample script was provided and I am not sure if this is even odata V2 or odata V3 problem. Re-open if the problem still persist with more...

Apart from the line comment, your change fails builds because of linter failure. Relevant for you is the: ************* Module pyodata.v2.service pyodata/v2/service.py:143: [C0301(line-too-long), ] Line too long (134/120) `the getsizeof...

I think it is generally OK. I would like split the "service block" to distinguish somehow "metadata invalid" use case for usage pyodata for example only as metadata validator -...

@filak-sap Hi, could you pls check this one as well?

After merging of #102 this issue seems to be ready to be closed. @bip91 could you confirm that latest head 7972f31 works for you? I will create release 1.5.0 soon.

Note: Current list of type checkers in Python to choose from is: Mypy, Pyre, Pyright. As (perhaps practical, not exact) alternative to marking the code with type annotations, one can...

Hi @maciekwolus. I am sorry, but the provided info is so scarce and so confusing that I cannot find anything actionable, nor even properly understand the question. What exact problem...

Closing for no response from issue author, if still valid, please re-open with more information as described in my previous comment.

Hi, the UPSERT feature was new in OData spec version 4. This enh. request is basically subtask of issue #39.

Build is failing due #130