As a user, I can specify Remote.includes with a pipenv.lock files

Open
#346 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by locating the existing requirements.txt workflow for Remote.includes in this repository, then review the linked Pipenv documentation and the original Redmine issue. Done means Remote.includes handles pipenv.lock files with behavior matching the requirements.txt workflow, including appropriate test coverage.

Written by the indexing model from the issue text.

Description

feature request

Original Pulp Redmine Issue: https://pulp.plan.io/issues/4713

This is identical to the requirements.txt workflow, but with pipenv.lock files

https://pipenv.readthedocs.io/en/latest/

Dominant language
Python
Stars
49
Forks
88
Avg merge
1d 10h
Merged PRs (30d)
31

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pulp/pulp_python

All issues in pulp/pulp_python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.