Check the version of python and cuda with each image of cpu and gpu.
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker, python
- Domain
- documentation, release
Research direction
Start by locating the CPU and GPU image definitions and the v139 release-note workflow. Identify how Python and CUDA versions can be checked without rebuilding the images, then document the versions for each image and that check. Done means both image variants have version information in the release notes and a practical inspection method is documented.
Written by the indexing model from the issue text.
Description
🚀 Feature
I couldn't find the python and cuda version of the each image of cpu and gpu for v139 right away, so could you put it in the release notes? By the way, is there a way to immediately check the versions of python and cuda? It is troublesome to build an image of about 50GB each time.
Motivation
The cuda versions of kaggle's gpu and cpu images often change, so even if you refer to an old notebook, it is difficult to align the environment with the current version. For example, it is troublesome to prepare an old version of mmdetection wheel.
Additional context
There is nothing special other than the above.
- Dominant language
- Python
- Stars
- 2.7k
- Forks
- 1k
- Avg merge
- 7h 38m
- Merged PRs (30d)
- 9
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Kaggle/docker-python
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Kaggle/docker-python#1482 · 2 reactions ·
Maintainers usually reply within 1 day
-
loraOpen
Difficulty 5/5 Over a week Newbie friendliness 20/100
Kaggle/docker-python#1564 ·
Maintainers usually reply within 1 day
-
bug help wanted
Difficulty 3/5 1-2 days Newbie friendliness 25/100
Kaggle/docker-python#1563 ·
Maintainers usually reply within 1 day
-
ذOpen
Difficulty 5/5 Over a week Newbie friendliness 1/100
Kaggle/docker-python#1555 ·
Maintainers usually reply within 1 day
-
Pytorch CUDA P100 GPU IncompatibilityPossibly taken @shivansh193 claimed this 76 days ago. Openbug help wanted
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Kaggle/docker-python#1546 · 4 comments · 2 reactions ·
Maintainers usually reply within 1 day
All issues in Kaggle/docker-python
Similar issues
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 74/100
BrainLesion/BraTS#200 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
OpenHands/extensions#970 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
rl-institut/enetra#91 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
huggingface/datasets#9100 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/garak#2486 · 1 comment ·
Maintainers usually reply within 2 days