Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add current workdir to pythonpath automatically
See original GitHub issueDescription of Problem:
Using the new rasa commands doesn’t automatically load the current workdir as a potential module directory anymore, which means peoples custom components don’t work (https://github.com/RasaHQ/rasa/issues/3748). They have to manually add them to their PYTHONPATH, which with the old python -m way wasn’t necessary
Overview of the Solution: We should consider adding the current workdir as a potential module directory automatically on startup
Issue Analytics
- State:
- Created 4 years ago
- Comments:19 (15 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@shubh802 Could you please ask the question in the forum? Both, Rasa team members and the Rasa community, will help you there 🙂 Thanks 🙏
I just mean when i’m testing commands and stuff. I’ll add it to mine while I work on a PR today that involves testing commands and see if anything funky happens