Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use a clearly synthetic filename when compiling code #593 #594

Merged
merged 1 commit into from Nov 29, 2021

Conversation

nedbat
Copy link
Contributor

@nedbat nedbat commented Mar 19, 2021

Using just the source as the file name confuses tools like coverage.py
that analyze code execution. Using angle brackets makes clear that this
is not a real file.

Using just the source as the file name confuses tools like coverage.py
that analyze code execution.  Using angle brackets makes clear that this
is not a real file.
@nedbat
Copy link
Contributor Author

nedbat commented Nov 10, 2021

Any opinions on this?

@sashaaero
Copy link
Member

Hello, sorry for a long reply. Thanks for your Pull Request.

@sashaaero sashaaero merged commit 8926482 into ponyorm:orm Nov 29, 2021
kozlovsky added a commit that referenced this pull request Jan 10, 2022
# Features

* Add Python 3.10 support, drop support of Python < 3.7

# Bugfixes

* Do not perform optimistic checks when deleting an object (it is OK if it was already deleted by concurrent transaction)
* Validation of int fields should take into account field size and check that the value is fit into the range
* More tests for hybrid methods added
* Fix incorrect assertion check `assert t is translator.`
* Fix aggregated query `sum(x.field for x in previous_query)`
* #594: Use a clearly synthetic filename when compiling dynamic code to not confuse coverage.py
* Use DecompileError exception instead of AssertionError when a function cannot be decompiled
kozlovsky added a commit that referenced this pull request Jan 27, 2022
# Features

* Add Python 3.10 support, drop support of Python < 3.7
* You can create an in-memory SQLite database accessible from multiple threads by specifying ":sharedmemory:" as a file name

# Bugfixes

* Do not perform optimistic checks when deleting an object (it is OK if it was already deleted by concurrent transaction)
* Validation of int fields should take into account field size and check that the value is fit into the range
* More tests for hybrid methods added
* Fix incorrect assertion check `assert t is translator.`
* Fix aggregated query `sum(x.field for x in previous_query)`
* #594: Use a clearly synthetic filename when compiling dynamic code to not confuse coverage.py
* Use DecompileError exception instead of AssertionError when a function cannot be decompiled
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants