Expose IdDiscrete, Hamming, BID as top-level dadapy imports#177
Merged
Conversation
… not parent package
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
dadapy/__init__.pynow exposesIdDiscrete(replacingfrom .id_discrete import *) and addsBID,Hammingfromdadapy.hammingnotebook_on_discreteID.ipynb,notebook_hamming.ipynb), and one docstring example inid_discrete.pyto use the new short-form imports.Related
Related to #156:
from dadapy import BID, Hammingsyntax is supported, consistently with the classes imported from all the other modules of the packageTest plan
pytest tests/test_id_discrete/test_discrete_id.py— 2/2 passing locallypython tests/test_hamming/test0.py— script runs end-to-end, BID optimization converges with expected values