CHEFGP (OCT17) [PYTHON]
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 64
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Description
- [X] Issue Title is in form `Problem Code (Contest Code) [Language]`
- [X] I ensure I'm Eligible as per [ECR](https://github.com/iiitv/ChefLib/blob/master/README.md#ecr).
- [X] I got AC for this problem when the contest was live. (Not necessary, but appreciable).
- [X] I have checked that my solution is passing on Problem (in case you make some changes).
- [X] I will send my PR only after I'm assigned to this issue by any maintainer.
- [X] I ensure that I'm not assigned to more than 2 issues.
- [X] Assign this issue to me (I want to work on this).
##### It's not necessary for all for points to be checked, we will look at what is required once you open an issue.
Contributor guide
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.
Research direction
The issue identifies the CHEFGP problem from the OCT17 contest and requests a Python solution, but it names no source file, test, entry point, or problem details. Start by locating the repository's existing contest-solution layout and the CHEFGP statement; done means a Python solution is added in the expected location and passes the problem's judge.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100