Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

testArg_subresource_Text fails on 3.13.1; additional errors on 3.13.1, 3.11.9 [macOS]

Aperta
  • Qualcosa non va?
#62 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
python
Ambito
testing-qa

Direzione di ricerca

Run python -m tests using the reproduction environment and inspect tests/test_module_api.py, tests/test_module_cache.py, and api.py:37. Compare the failing Hypothesis examples with the cache setup and teardown paths, including cache.API_CACHE and cache.CACHE_DIR. Done means the reported failures and errors are resolved across the stated Python versions and the full test suite passes.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Operating system: macOS Sequoia 15.2, M3 chip, 2024

To reproduce:

python -m venv ~/pokebase-env
source ~/pokebase-env/bin/activate
# export PATH=$HOME/pokebase-env/bin:$PATH
python -m pip install -U pip
git clone https://github.com/PokeAPI/pokebase
cd pokebase
# git checkout 1.4.0  # also observed on d40c95ce41e62e1d97cefa4ad4ee8d0500c423d9
python -m pip install -e .
python -m pip install hypothesis
python -m tests

Expectation: 0 failures

Observation (on Python 3.13.1):

======================================================================
FAIL: testArg_subresource_Text (tests.test_module_api.TestFunction_get_data.testArg_subresource_Text)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/opt/homebrew/Cellar/[email protected]/3.13.1/Frameworks/Python.framework/Versions/3.13/lib/python3.13/unittest/mock.py", line 1420, in testArg_subresource_Text
    def patched(*args, **keywargs):
           ^^^^^^^^^^^^^^^^^^^^
  File "/Users/pikalaxalt/pokebase-env/lib/python3.13/site-packages/hypothesis/core.py", line 1787, in wrapped_test
    raise the_error_hypothesis_found
  File "/opt/homebrew/Cellar/[email protected]/3.13.1/Frameworks/Python.framework/Versions/3.13/lib/python3.13/unittest/mock.py", line 1424, in patched
    return func(*newargs, **newkeywargs)
  File "/Users/pikalaxalt/pokebase/tests/test_module_api.py", line 106, in testArg_subresource_Text
    self.assertIsNotNone(api.get_data(endpoint, resource_id, subresource).get('version_details'))
    ~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError: unexpectedly None
Falsifying example: testArg_subresource_Text(
    <tests.test_module_api.TestFunction_get_data testMethod=testArg_subresource_Text>,
    endpoint='ability',
    resource_id=1,
    subresource='',
)
Explanation:
    These lines were always and only run by failing examples:
        /Users/pikalaxalt/pokebase/pokebase/api.py:37
        /opt/homebrew/Cellar/[email protected]/3.13.1/Frameworks/Python.framework/Versions/3.13/lib/python3.13/shelve.py:114

Additionally the following errors are observed in both this version and under python 3.11.9:

======================================================================
ERROR: testEnv_CacheFileNotFound (tests.test_module_cache.TestFunction_load.testEnv_CacheFileNotFound)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/pikalaxalt/pokebase/tests/test_module_cache.py", line 112, in testEnv_CacheFileNotFound
    resource_id=integers(min_value=1))
        ^^^^^^^
  File "/Users/pikalaxalt/pokebase-env/lib/python3.13/site-packages/hypothesis/core.py", line 1787, in wrapped_test
    raise the_error_hypothesis_found
  File "/Users/pikalaxalt/pokebase/tests/test_module_cache.py", line 116, in testEnv_CacheFileNotFound
    os.remove(cache.API_CACHE)
    ~~~~~~~~~^^^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: '/Users/pikalaxalt/pokebase/testing/api.cache'
Falsifying example: testEnv_CacheFileNotFound(
    self=<tests.test_module_cache.TestFunction_load testMethod=testEnv_CacheFileNotFound>,
    endpoint='ability',
    resource_id=1,
)

======================================================================
ERROR: testEnv_CacheFileNotFound (tests.test_module_cache.TestFunction_save.testEnv_CacheFileNotFound)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/pikalaxalt/pokebase/tests/test_module_cache.py", line 59, in testEnv_CacheFileNotFound
    endpoint=sampled_from(ENDPOINTS),
        ^^^^^^^
  File "/Users/pikalaxalt/pokebase-env/lib/python3.13/site-packages/hypothesis/core.py", line 1787, in wrapped_test
    raise the_error_hypothesis_found
  File "/Users/pikalaxalt/pokebase/tests/test_module_cache.py", line 63, in testEnv_CacheFileNotFound
    os.remove(cache.API_CACHE)
    ~~~~~~~~~^^^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: '/Users/pikalaxalt/pokebase/testing/api.cache'
Falsifying example: testEnv_CacheFileNotFound(
    self=<tests.test_module_cache.TestFunction_save testMethod=testEnv_CacheFileNotFound>,
    data={'': ''},
    endpoint='ability',
    resource_id=1,
)

======================================================================
ERROR: testEnv_CacheDirNotFound (tests.test_module_cache.TestFunction_set_cache.testEnv_CacheDirNotFound)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/pikalaxalt/pokebase/tests/test_module_cache.py", line 172, in testEnv_CacheDirNotFound
    os.rmdir(cache.CACHE_DIR)
    ~~~~~~~~^^^^^^^^^^^^^^^^^
OSError: [Errno 66] Directory not empty: '/Users/pikalaxalt/pokebase/testing'
Lingua principale
Python
Stelle
361
Fork
58
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Non abbiamo ancora controllato i file di configurazione di questo progetto. Parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di PokeAPI/pokebase

Tutte le issue di PokeAPI/pokebase

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.