Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Fix python-3.6 CircleCI tests

Open
  • Is something wrong?
#120 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
32/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
ci-cd, testing

Research direction

Start with the failing CircleCI Python 3.6 job and inspect tests/requirements.txt, focusing on the pytest-cookies, pytest, cryptography, and pip versions shown in the log. Re-run the Python 3.6 test job after investigating the dependency conflict; done means the job completes successfully without the reported installation failure.

Written by the indexing model from the issue text.

Description

Seems like it's currently failing:

#!/bin/bash -eo pipefail
. venv/bin/activate
pip install -r tests/requirements.txt --quiet

pytest-cookies 0.5.1 has requirement pytest<6.0.0,>=3.3.0, but you'll have pytest 6.2.2 which is incompatible.
Command "/home/circleci/project/venv/bin/python -u -c "import setuptools, tokenize;__file__='/tmp/pip-install-7nfc7x4u/cryptography/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-record-fhb8jvs6/install-record.txt --single-version-externally-managed --compile --install-headers /home/circleci/project/venv/include/site/python3.6/cryptography" failed with error code 1 in /tmp/pip-install-7nfc7x4u/cryptography/
You are using pip version 18.1, however version 21.0.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.

Exited with code exit status 1
CircleCI received exit code 1
Dominant language
Python
Stars
294
Forks
196
No merged PRs in 30d

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

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 plotly/dash-component-boilerplate

All issues in plotly/dash-component-boilerplate

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.