-
Notifications
You must be signed in to change notification settings - Fork 29
Support bazel repositories by documenting environment file format #45
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
Comments
Those folders are unpacked wheels that contain a
|
Hi @jlisee, trying to catch up here since TJ is out on leave. Could you clarify the following for me:
|
Blocked? Fixed?
|
With the latest configuration changes from #77, I think this should be possible now (and should also re-use any existing pyright configuration you have). Does the current README give you enough info to do what you're looking for? |
Is your feature request related to a problem? Please describe.
When trying to run
scip-python
on my Bazel based repository with a non-standard requirements.txt location and no use ofpip
the program locks up in theEvaluating python environment dependencies
stage.Describe the solution you'd like
I would like to be able to generate the dependency map myself since our repository installs dependencies through Bazel, hence files are in non-standard locations and the requirements.txt file has a non-standard location and path.
We have enough automation in place that will be straight forward to maintain, and way easier than trying to tool to understand our build system.
Additional context
Pyright
itself works fine with just using[tool.pyright] extraPaths
in ourpyproject.toml
to find these locations, a sample simple configuration:The text was updated successfully, but these errors were encountered: