Skip to content

ParaView version #162

Open
Open

Description

@huiwanpnnl

A reviewer of the JOSS paper asked "if there were significant updates to ParaView, would that hinder the functining of your package?"

Did I understand correctly that this might happen?

Relatedly, I see that our quickview-env.yml lists paraview>=6. Would it make sense to specify a particular version and manually update that in the future?

Activity

  1. self-assigned this
    on Nov 6, 2026
  2. jourdain commented on Nov 6, 2026

    @jourdain
    Collaborator

    We could but normally the API we rely on from ParaView is pretty stable. So the likelihood of something broken is low, but it does exist.

    If we limit the version of ParaView, we may prevent another package from the same conda environment to leverage the latest ParaView capabilities.

  3. huiwanpnnl commented on Nov 6, 2026

    @huiwanpnnl
    CollaboratorAuthor

    I see. Then we should probably leave the paraview>=6 as is. And we can work together to prepare a response to the reviewer.

  4. huiwanpnnl commented on Nov 8, 2026

    @huiwanpnnl
    CollaboratorAuthor

    PR #165 includes a new doc page on system requirements, which clarifies that for users, there is no need to separately install ParaView.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

JOSSFor the JOSS paper on QuickView

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions