[BUG]: Remove obsolete PyPI logging dependency from pyproject.toml

Aperta
#167 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

@agarwalpranav0711 ci sta già lavorando.

Dal 12/10/2026.

  • #168 di @agarwalpranav0711 — aperta

Valutazione

Difficoltà
1/5
Tempo stimato
Meno di un'ora
Idoneità per principianti
1/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Ferma
Stack tecnologico
python
Ambito
build-system

Direzione di ricerca

The issue names backend/pyproject.toml, uv.lock, and the setup command in CONTRIBUTING.md. Read the dependency entry and reproduce the clean setup with uv sync --no-build-isolation; done means the obsolete logging pin is removed, the lockfile is updated, and the documented command succeeds. An open linked pull request already covers this work.

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

Descrizione

bug
Bug Description

backend/pyproject.toml pins "logging>=0.4.9.6". logging has been a standard library module since Python 2.3 and does not need to be installed from PyPI.

The PyPI logging package is an unmaintained source distribution from 2008 without prebuilt wheels. Running the backend setup command documented in CONTRIBUTING.md (uv sync --no-build-isolation) fails on a clean setup because the package requires setuptools to build from source, which is not pre-installed in the environment. While plain uv sync succeeds using an isolated build sandbox, pinning this obsolete distribution adds unnecessary build overhead and breaks the documented setup instructions.

I used an AI assistant to help investigate the root cause, and I reproduced and verified all behavior locally in a clean virtual environment.

I would like to work on this issue and submit a PR to remove the pin and update uv.lock.

Steps to Reproduce
  1. In a clean environment without pre-installed setuptools, navigate to backend/
  2. Run: uv sync --no-build-isolation
Logs and Screenshots
  × Failed to build `logging==0.4.9.6`
  ├─▶ The build backend returned an error
  ╰─▶ Call to
      `setuptools.build_meta:__legacy__.prepare_metadata_for_build_wheel`
      failed (exit code: 1)

      [stderr]
      Traceback (most recent call last):
        File "<string>", line 8, in <module>
          from setuptools.build_meta import __legacy__ as backend
      ModuleNotFoundError: No module named 'setuptools'
Environment Details
  • OS: Windows 11 (affects clean Linux/macOS environments as well)
  • Python: 3.13
  • uv: 0.11.21
Impact

Medium - Feature works but has issues

Code of Conduct
  • I have joined the Discord server and will post updates there
  • I have searched existing issues to avoid duplicates
Lingua principale
TypeScript
Stelle
58
Fork
90
Merge medio
11h 51m
PR unite (30g)
3

Preparare l'ambiente

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 AOSSIE-Org/Perspective

Tutte le issue di AOSSIE-Org/Perspective

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.