Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
D
dorie
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 31
    • Issues 31
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 9
    • Merge Requests 9
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • dorie
  • dorie
  • Issues
  • #31

Closed
Open
Opened Sep 12, 2017 by Lukas Riedel@lriedel🛀Owner

Python venv setup does not allow active code development

In our current dune-venv setup the packages installed are not replaced/updated upon configuring once the source files changed. Running the appropriate CMake command with ADDITIONAL_PIP_PARAMS --force-reinstall --upgrade --no-deps always upgrades the packages, but won't install any required packages that could be retrieved from the web.

--upgrade alone does not work because pip is not able to reinstall other Dune module dependencies.

--force-reinstall alone dubiously seems to have no effect at all.

One workaround might be to place all requirements into a requirements.txt file again, like before. However, it remains unclear then how --upgrade can be called if another Dune Python module is specifically required.


see Issue 81 on dune-common for reference

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: dorie/dorie#31