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

Add vg.compat forward-compatibilty layer for libraries #158

Merged
merged 8 commits into from
Jul 13, 2021
Merged

Conversation

paulmelnikow
Copy link
Member

@paulmelnikow paulmelnikow commented Jul 10, 2021

Closes #112

Depends on #157

This is possible since `poetry` installs the project into the venv by default. It helps ensure that functions under test are properly exported in `__all__`.
@paulmelnikow paulmelnikow changed the title Add vg.compat compatibilty layer for libraries Add vg.compat forward-compatibilty layer for libraries Jul 10, 2021
stacks of inputs interchangeably. They return The Right Thing – a single
result or a stack of results – without the need to reshape inputs or outputs.
With the power of NumPy, the vectorized functions are fast.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why drop all of this documentation from the README?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's duplicated from the documentation, and that seems like a better place for it: https://vgpy.dev/

@@ -0,0 +1,21 @@
import numpy as np
import pytest
import vg.compat.v1 as vg
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

# Conflicts:
#	doc/index.md
@paulmelnikow paulmelnikow merged commit 900413e into main Jul 13, 2021
@paulmelnikow paulmelnikow deleted the compat branch July 13, 2021 20:41
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.

Add a compatibility layer
2 participants