-
Notifications
You must be signed in to change notification settings - Fork 659
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
Change name of asel
in timeseries to something more comprehensible.
#3911
Comments
yes, please, |
|
yeah, you're right |
@MDAnalysis/gsoc-mentors making this a gsoc-starter issue |
@hmacdope isn't this a 3.0 targeted change? We wouldn't be able to merge it during the application period. |
Ah yes sorry I meant the deprecation warning part. Do we think that is suitable ? |
Sounds good to me! |
hi @hmacdope, I want to work on MDAnalysis as part of GSoC and wanted to take up this issue. Seems like it won't get merged during the application period. However, can I work on it? |
Please go ahead and make a PR! If you make a fix it can be merged in the application period. |
Hi @hmacdope I have made changes for asel in timeseries wherever the function is defined and called. I have also made changes in the test code for the same. Do you think sample_atom_group is a good variable name in place of asel (can be a little wordy)? atom_group and atomgroup are used as variable/function names in a couple of files. Also, I didn't understand the discussion regarding the deprecation warning, can you explain it a bit? |
@hmacdope I'm reopening to keep an issue to track the removal of asel - please do reclose if there's another one already. |
Cheers, nah this is it. |
Originally posted by @IAlibay in #3890 (comment)
I agree with @IAlibay that the name
asel
is a little confusing and could do with a change in 3.0.leave your opinions below.
Will require a deprecation warning first if we go ahead.
The text was updated successfully, but these errors were encountered: