Refactor package creation support code into a common location

Offen
#59,608 22 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
25/100
Issue-Typ
Refactoring
Klarheit
Muss geklärt werden
Aktivitätsstatus
Veraltet
Tech-Stack
python
Bereich
testing

Rechercherichtung

Start by reviewing the three linked patches for issue-15403 and the dependency issues, especially the move from test/support.py to the test.support subpackage and documentation for test.support.script_helper. Trace the package-creation support code and its tests, then verify that the helpers have one common location and the relevant test suite passes.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

tests type-refactor
BPO 15403
Nosy @ncoghlan, @pitrou, @vstinner, @merwok, @cjerdonek, @ericsnowcurrently
Dependencies
  • bpo-15494: Move test/support.py into a test.support subpackage
  • bpo-18576: Document test.support.script_helper
  • bpo-19700: Update runpy for PEP 451
    		•
    Files
  • issue-15403-1.patch
  • issue-15403-2.patch
  • issue-15403-3.patch
    		•

    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 2012-07-20.11:13:12.663>
labels = ['tests']
title = 'Refactor package creation support code into a common location'
updated_at = <Date 2019-07-29.11:44:38.181>
user = 'https://github.com/cjerdonek'

    bugs.python.org fields:

    activity = <Date 2019-07-29.11:44:38.181>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Tests']
creation = <Date 2012-07-20.11:13:12.663>
creator = 'chris.jerdonek'
dependencies = ['15494', '18576', '19700']
files = ['26447', '26670', '30870']
hgrepos = []
issue_num = 15403
keywords = ['patch']
message_count = 22.0
messages = ['165910', '165912', '166499', '166759', '166771', '166773', '166774', '166776', '166778', '166787', '166788', '166790', '166793', '166844', '166847', '166850', '167266', '192708', '193822', '193823', '205639', '348630']
nosy_count = 7.0
nosy_names = ['ncoghlan', 'pitrou', 'vstinner', 'eric.araujo', 'chris.jerdonek', 'eric.snow', 'italip']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue15403'
versions = ['Python 3.3']

    Vorherrschende Sprache
    Python
    Sterne
    77.2k
    Forks
    36k
    Ø Merge
    1 T. 9 Std.
    Gemergte PRs (30 T.)
    558

    Beitragsleitfaden

    Beitragsleitfaden öffnen

    Erste Schritte

    1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
    2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
    3. Forken Sie das Repository und arbeiten Sie in einem Branch.
    4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

    Mehr aus python/cpython

    Alle Issues in python/cpython

    Ähnliche Issues

    Weitere Issues zu Python

    Neue Issues direkt in Ihr Postfach

    Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.