-
Notifications
You must be signed in to change notification settings - Fork 667
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 py3.13 support w/ minimal deps #4732
Changes from 6 commits
e8323ad
ecd6807
6add21e
dba9ffc
23d06e7
ab6773e
c84eecb
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -345,17 +345,17 @@ def test_verbose_progressbar(u, capsys): | |
def test_verbose_progressbar_run(u, capsys): | ||
FrameAnalysis(u.trajectory).run(verbose=True) | ||
_, err = capsys.readouterr() | ||
expected = u'100%|██████████| 98/98 [00:00<00:00, 8799.49it/s]' | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think the reason why the full output was there originally was to give devs an idea what it looks like even if other parts could not be reliably tested. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Unfortunately the py3.13 behaviour changed here and I can't work out exactly why - I'm not sure if there's a better way to deal with this without having an explicit python version check :/ |
||
expected = u'100%|██████████' | ||
actual = err.strip().split('\r')[-1] | ||
assert actual[:24] == expected[:24] | ||
assert expected == actual[:15] | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why did you switch actual and expected? Doesn't really matter except for consistency throughout because in testsuite/MDAnalysisTests/lib/test_log.py it's still actual == expected. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I had originally switched it to a There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Reverted the order in the latest commit. |
||
|
||
def test_verbose_progressbar_run_with_kwargs(u, capsys): | ||
FrameAnalysis(u.trajectory).run( | ||
verbose=True, progressbar_kwargs={'desc': 'custom'}) | ||
_, err = capsys.readouterr() | ||
expected = u'custom: 100%|██████████| 98/98 [00:00<00:00, 8799.49it/s]' | ||
expected = u'custom: 100%|██████████' | ||
actual = err.strip().split('\r')[-1] | ||
assert actual[:30] == expected[:30] | ||
assert expected == actual[:23] | ||
|
||
|
||
def test_progressbar_multiprocessing(u): | ||
|
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.
did you mean to change to
3.13
above? I don't think that's a blocker here though