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

Pokemon Information Error

Open
#37 2 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
api

Research direction

Start by reproducing the Pokedex initialization described in the issue and isolate the first failing Pokémon, beginning with deoxys. Compare the failing height access with the standalone .height access, then verify that initialization completes for all 898 Pokémon and that the listed cases no longer require the try/except workaround.

Written by the indexing model from the issue text.

Description

Screen Shot 2022-03-16 at 22 13 24

So I have the really clunky, awful code above in a program I am running (I know there are functions to do this, but I had to do it on my own using certain commands for a class), and I am trying to initialize a "Pokedex" for all 898 Pokemon. However I keep getting height errors for the following Pokemon:
deoxys
wormadam
giratina
shaymin
basculin
darmanitan
tornadus
thundurus
landorus
keldeo
meloetta
meowstic
aegislash
pumpkaboo
gourgeist
zygarde
oricorio
lycanroc
wishiwashi
minior
mimikyu
toxtricity
eiscue
indeedee
morpeko
urshifu

I don't exactly know what the error is, but I know it doesn't like it and I had to add the try/except here so it would at least initialize what it could. I just no it freaks out whenever it gets to those Pokemon, so I thought I would let you know.
Screen Shot 2022-03-16 at 22 11 39

This is a screenshot of the error that I get when it gets to deoxys, again not sure why that's happening because when I use the .height outside of this function for deoxys, it works just fine.
Please let me know, thank you.

Dominant language
Python
Stars
361
Forks
58
PR merge metrics
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 PokeAPI/pokebase

All issues in PokeAPI/pokebase

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.