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

Error: name 'CMakePackage' is not defined #8292

Closed
junghans opened this issue May 27, 2018 · 7 comments
Closed

Error: name 'CMakePackage' is not defined #8292

junghans opened this issue May 27, 2018 · 7 comments
Labels

Comments

@junghans
Copy link
Contributor

I getting a:

$ spack spec flang@develop
Input spec
--------------------------------
flang@develop

Concretized
--------------------------------
==> Error: name 'CMakePackage' is not defined

but only when using python3.5.5, python-2.7.14 works fine.

@healther
Copy link
Contributor

healther commented May 27, 2018

You'll need to clean pythons cached files, see #8090 (comment) for how to do that. This is a consequence of a refactoring and for some reason only happens for python3

@tgamblin this should get a more prominent issue, so that people can find the solution for themselves without following the issues closely ... Any idea of how to achieve that?

@junghans
Copy link
Contributor Author

Worked, thanks!

@adamjstewart
Copy link
Member

@healther We could add it to Known Issues but I'm not sure how many people are using Python 3, and it isn't a permanent issue.

@healther
Copy link
Contributor

Yeah... maybe it should go there. I agree that it should not be a permanent issue, but this is the third separate issue that was opened for this problem...

@adamjstewart
Copy link
Member

@junghans Now that #8419 has been merged, do you think it's safe to close this issue? Or should we add something to "Known Issues"? I think the number of Python 3 users is small enough that we can continue putting out fires on GitHub. I don't know how many people actually read "Known Issues" anyway.

@junghans
Copy link
Contributor Author

junghans commented Jun 7, 2018

Sure!

@junghans junghans closed this as completed Jun 7, 2018
@healther
Copy link
Contributor

healther commented Jun 7, 2018

I think the number of Python 3 users is small enough that we can continue putting out fires on GitHub.

I had this today on a python2 based system, but I can't give you the sequence of steps to reproduce it, I just implemented the clean and washed my hands of it

I don't know how many people actually read "Known Issues" anyway.

Yeah... I'm not sure if it's even part of the stub issue that you get if you start a new one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants