Skip to content
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

Python wrapper: SetQuery and ExpandQuery for bonds #3172

Merged
merged 1 commit into from
May 19, 2020

Conversation

i-tub
Copy link
Contributor

@i-tub i-tub commented May 15, 2020

Basically copied over these two wrappers from Atom.cpp to Bond.cpp.

What does this implement/fix? Explain your changes.

Added the wrappers for completeness / consistency between QueryAtom and QueryBond, and because they'd actually be useful in a program in which I want to modify SMARTS patterns programmatically. (My workaround until now had been to convert to an EditableMol, delete the bond, and add a new bond to replace it. And still isn't as flexible.)

Basically copied over these two wrappers from Atom.cpp to Bond.cpp.
Copy link
Member

@greglandrum greglandrum left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@greglandrum greglandrum added this to the 2020_09_1 milestone May 19, 2020
@greglandrum
Copy link
Member

It's "amusing" that the definition of expandQuery() that you needed was already in Bond.cpp but not exposed. :-S

@greglandrum greglandrum merged commit 21d5ec6 into rdkit:master May 19, 2020
@greglandrum greglandrum modified the milestones: 2020_09_1, 2020_03_3 May 29, 2020
@greglandrum
Copy link
Member

Relabeling this as a bug because this is fixing an oversight and is risk free for downstream code.

greglandrum pushed a commit that referenced this pull request Jun 9, 2020
Basically copied over these two wrappers from Atom.cpp to Bond.cpp.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants