6.19.1: circular build dependency in testing procedure

Open
#1,052 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
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
build-system, testing-qa

Research direction

The issue names no files, tests, or entry points. Start by reviewing the ipykernel testing procedure and packaging dependency metadata, then trace the ipyparallel-to-ipykernel dependency loop; done means the circular build dependency and its effect on package ordering are resolved.

Written by the indexing model from the issue text.

Description

Looks like ipykernel test suite requires ipyparallel which requires ipykernel.
This creates kind of loop in dependencies when ipykernel will be tested in end with installed ipyparallel and older version of the ipykernel.

For now I don't see any issues in case of ipykernel testing however potentially it may be cause some issue however that loop in build dependencies creates some difficulties in case of packaged distribution resources ordering procedures.

Dominant language
Python
Stars
734
Forks
411
Avg merge
1d 2h
Merged PRs (30d)
9

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 ipython/ipykernel

All issues in ipython/ipykernel

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.