Closed shashank-iitbhu closed 6 months ago
I have already tested this locally. Let me know if these changes can help. Open for discussion. cc @andrewtavis @wkyoshida Should I open a PR, so that you can also test this?
Makes sense to me, @shashank-iitbhu! Feel free to send along a PR 🚀 I'll send along the structure changes right now, so if you could bring those into your branch before that'd be great 😊
2b72e64 just sent along the directory structure update, @shashank-iitbhu, so you're good to pull in the changes and send along a PR for this :)
Opened a PR for these changes.
@andrewtavis This I believe highlights the need to include instructions for using pip install -e .
in our contributing guide or documentation.
@andrewtavis and @shashank-iitbhu please is this issue still opened?
@andrewtavis and @shashank-iitbhu please is this issue still opened?
I have linked a PR above, haven't been merged yet. It's still under review.
Closed in #123 🚀 Thank you, @shashank-iitbhu!
Terms
Behavior
Description
Currently, in several scripts within the Scribe-Data project, we are modifying
sys.path
to include thesrc/scribe_data
directory to ensure that thescribe_data
module can be imported correctly. For example,This can lead to potential issues with import resolution and is generally not considered a best practice.
Suggested Changes
sys.path
.from scribe_data import module_name
pip install -e .
from the project root directory. This allows for testing changes to the code without needing to reinstall the package.sys.path
list to determine where to look for modules to import. After we have built the modules usingpip install -e .
, thescribe_data
module will already be present insys.path
as it already has path to pip packages and then we do not need to addsrc/scribe_data
explicitly tosys.path
.