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

Abierto
#167 1 comentario 0 reacciones 0 asignados Ver en GitHub

@agarwalpranav0711 ya está trabajando en esto.

Desde el 12/10/2026.

  • #168 de @agarwalpranav0711 — abierto

Evaluación

Dificultad
1/5
Tiempo estimado
Menos de una hora
Aptitud para principiantes
1/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
python
Área
build-system

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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
Lenguaje dominante
TypeScript
Estrellas
58
Forks
90
Merge medio
11 h 51 min
PR fusionados (30 d)
3

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de AOSSIE-Org/Perspective

Todos los issues de AOSSIE-Org/Perspective

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.