Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • ParaView ParaView
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 2k
    • Issues 2k
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 83
    • Merge requests 83
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ParaViewParaView
  • ParaViewParaView
  • Issues
  • #19981
Closed
Open
Issue created Jun 09, 2020 by Ethan Stam@ethan.stamDeveloper

Remove unnecessary Python 2 conflict in ParaView's Spack file

@utkarsh.ayachit @patchett2002 @pflarr

In ParaView's Spack package file, there is a conflict preventing users from building newer ParaView versions with Python 2. This should be removed, because it is an unnecessary conflict and a boundary preventing LANL code teams from moving to newer ParaView versions.

https://github.com/spack/spack/blob/2421d903b034c92660fbe999b7d486e6f21a7417/var/spack/repos/builtin/packages/paraview/package.py#L54

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking