-
Notifications
You must be signed in to change notification settings - Fork 10
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
Fix failing tests and documentation #684
Conversation
Codecov Report
@@ Coverage Diff @@
## master #684 +/- ##
=======================================
Coverage 96.07% 96.08%
=======================================
Files 92 92
Lines 6325 6327 +2
=======================================
+ Hits 6077 6079 +2
Misses 248 248
Continue to review full report at Codecov.
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
Finally, I got the documentation bug fixed... sort of (see here). During the process I went nuts and adjusted all imports to import from the correct module instead of the global weldx namespace. Maybe we have to review where we want to undo that (doc examples, tutorials?). On the plus side, it should probably also fix some circular imports that poped up every now and then. |
Thanks for fixing this pandas issue. Was it really mandatory to change all the imports? What was the exact error message? |
The fix for the pandas issue was the first commit and I just had to adjust the tests to the new behaviour. The fix for the documantation was the linked commit in my previous comment. So the import changes weren't mandatory. However, I couldn't reproduce the bug locally so I had to try it by committing over and over again. I initially thaught sphinx was getting the As I said, we can undo all the import changes, but I think at least some of them do make sense since I get circular import problems from time to time when I run the debugger. But in the notebooks and examples, I feel we should undo it since it bloats the code and gives the wrong impression that you always have to pick the correct module. Feel free to mark things to be undone. Maybe we can discuss this during todays jour fixe. This was the sphinx error message:
|
weldx/core.py
Outdated
>>> from weldx.core import GenericSeries | ||
>>> from weldx.constants import Q_ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is there a bug/import error when we import from the main weldx
namespace in the doctests?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See my comment above --- no there isn't.
Ok I just now caught up on the comments I think in the python package files it is better/safer to import from the correct namespace to avoid potential import errors. Regarding the pandas issues: |
regarding the sphinx error message I think this is mostly due to the fact that we have both elements |
The same thing applies to CSM and LCS for instance, since they live in their own modules and are pulled to the top-level namespace. So there was a trick, how to avoid this ambiguity, but I cannot wrap my head around it right now. |
Here you go: https://github.com/BAMWelDX/weldx/runs/4936771641?check_suite_focus=true |
Interesting, it looks like |
@CagtayFabry All the doc changes are undone and some additional corrections applied. If you find the time to revisit, that would be nice. Otherwise, I ll merge tomorrow |
Changes
__add__
functions so that we couldn't use+
with a pandas Type on the left-hand side and ourTime
class on the right-hand sideweldx.time.Time
vsweldx.Time
Related Issues
None
Checks
update manifest file