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

[DEFECT] RAVEN fails if pip3 is for different version of python than used for running RAVEN. #2336

Open
2 of 13 tasks
joshua-cogliati-inl opened this issue Jul 10, 2024 · 0 comments · May be fixed by #2337
Open
2 of 13 tasks

Comments

@joshua-cogliati-inl
Copy link
Contributor

Thank you for the defect report

Defect Description

If python is install such that pip3 is a different version of python than in the raven libraries environment, the build raven will fail.

This will fail when the tests are run because the built version will be a different version from the version that is imported.

Steps to Reproduce

Create two installs of python, and use one for the python command and the other for the pip3 command.

Expected Behavior

Raven can build python.

Screenshots and Input Files

No response

OS

Windows

OS Version

No response

Dependency Manager

CONDA

For Change Control Board: Issue Review

  • Is it tagged with a type: defect or task?
  • Is it tagged with a priority: critical, normal or minor?
  • If it will impact requirements or requirements tests, is it tagged with requirements?
  • If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
  • Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure

  • If the issue is a defect, is the defect fixed?
  • If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
  • If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
  • If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
  • If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant