pydoc for namespace packages indicates FILE as built-in

Abierto
#68,441 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
python
Área
documentation

Línea de trabajo

Start by reproducing the pydoc output for a namespace package and inspect how it labels FILE as built-in. The issue does not name a source file or test; done means the namespace package is no longer reported as a built-in, with coverage for the affected behavior.

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

Descripción

3.10 3.11 3.9 (EOL) stdlib type-bug
BPO 24253
Nosy @iritkatriel

Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2015-05-21.04:37:38.192>
labels = ['type-bug', 'library', '3.9', '3.10', '3.11']
title = 'pydoc for namespace packages indicates FILE as built-in'
updated_at = <Date 2021-12-07.13:28:04.970>
user = 'https://github.com/anntzer'

bugs.python.org fields:

activity = <Date 2021-12-07.13:28:04.970>
actor = 'Antony.Lee'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2015-05-21.04:37:38.192>
creator = 'Antony.Lee'
dependencies = []
files = []
hgrepos = []
issue_num = 24253
keywords = []
message_count = 2.0
messages = ['243728', '407924']
nosy_count = 1.0
nosy_names = ['iritkatriel']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue24253'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']

Lenguaje dominante
Python
Estrellas
77.2k
Forks
36k
Merge medio
1 d 9 h
PR fusionados (30 d)
558

Guía de contribución

Abrir la guía de contribución

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 python/cpython

Todos los issues de python/cpython

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.