Add Pipenv configuration allowing installation of pre-releases #104825
Labels
No Label
Meta
Good First Issue
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
Eevee & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds, Tests & Devices
Module
Python API
Module
Rendering & Cycles
Module
Sculpt, Paint & Texture
Module
User Interface
Module
VFX & Video
Priority
High
Priority
Low
Priority
Normal
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Information from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-manual#104825
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently there is an issue with Pipenv dependency resolution for pre-releases (see build #1717). Pipenv lockfile creation process prevents the installation of pre-release versions specified in the requirements file, which is default behavior (see docs). Since we added a new package
sphinx-basic-ng
in commit 4ec2c02, which only has pre-release versions, we need to be able to install it with Pipenv in our CI.By setting
allow_prereleases = true
in the Pipfile or by added the--pre
flag topipenv install
commands, pre-release versions can be installed successfully.This issue is tracking that change for BuildBot.
I have added
--pre
to thepipenv install
specifically for doc-manual pipelines.I deployed this change to the workers and successfully did a rebuild of #1720.