-
Notifications
You must be signed in to change notification settings - Fork 19
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 rdkit.egg-info directory #97
Comments
A pull request to support this would be welcome. |
egg-info files are usually generated automatically when the package is
installed. The typical use-case would be if you are performing a
development install of a package. e.g. `pip install -e path/to/rdkit`. That
will generate an installed link pointing to your rdkit directory and
generate the .egg-info directory automatically. (Note: this is based on my
previous experience, I haven't tested this specifically with rdkit).
Would you mind double checking that you can't pip install rdkit with the
`-e` option to get what you want? Is there some other workflow you are
trying to achieve?
…-Luke
On Mon, Mar 15, 2021 at 10:19 PM Francois Berenger ***@***.***> wrote:
A pull request to support this would be welcome.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#97 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIQO6TL5YIDE73Y4CVFHQSTTD3S7RANCNFSM4P6G7JWA>
.
|
@zymergen-luke to the best of my knowledge, rdkit cannot be installed with pip. |
Yes, this issue is about adding correct metadata no matter how it is installed. That would make tools see that RDkit is installed, and allow people to add it to their dependencies. The way things are now, trying to install a package depending on RDkit results in your package manager (likely pip) to complain that it can’t find a way to install RDkit, despite RDkit being already installed. |
Thanks for the clarification!
…-Luke
On Wed, Mar 17, 2021 at 1:53 AM Philipp A. ***@***.***> wrote:
Yes, this issue is about adding correct metadata no matter how it can be
installed.
That would make tools see that RDkit is installed, and allow people to add
it to their dependencies.
The way things are now, trying to install a package depending on RDkit
results in your package manager (likely pip) to complain that it can’t find
a way to install RDkit, despite RDkit being already installed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#97 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIQO6TMWQZYF2I23BKGU563TEBUZRANCNFSM4P6G7JWA>
.
|
Well, someone has to contribute this. |
This is an rdkit issue, so closing: |
That metadata allows tools like pip and IDEs to detect that the package is installed.
The text was updated successfully, but these errors were encountered: