makesetup should support .S source files

Open
#61,073 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
build-system

Research direction

Start by locating the makesetup build entry point and review the attached makesetup-asm.diff, which is the only referenced implementation artifact. Trace how source-file extensions are handled, then verify that a build containing .S sources completes successfully without regressing existing source types.

Written by the indexing model from the issue text.

Description

build
BPO 16869
Nosy @orsenthil
Files
  • makesetup-asm.diff
    		•

    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 2013-01-05.05:56:47.207>
labels = ['build']
title = 'makesetup should support .S source files'
updated_at = <Date 2013-01-06.05:31:07.544>
user = 'https://bugs.python.org/bennoleslie'

    bugs.python.org fields:

    activity = <Date 2013-01-06.05:31:07.544>
actor = 'bennoleslie'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Build']
creation = <Date 2013-01-05.05:56:47.207>
creator = 'bennoleslie'
dependencies = []
files = ['28574']
hgrepos = []
issue_num = 16869
keywords = ['patch']
message_count = 3.0
messages = ['179111', '179134', '179172']
nosy_count = 2.0
nosy_names = ['orsenthil', 'bennoleslie']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue16869'
versions = ['Python 3.4']

    Dominant language
    Python
    Stars
    77.2k
    Forks
    36k
    Avg merge
    1d 9h
    Merged PRs (30d)
    558

    Contributor guide

    Open the contributing guide

    First steps

    1. Read the whole issue, then the project's contributing guide.
    2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
    3. Fork the repository and make your change on a branch.
    4. Open a pull request that references the issue number.

    More from python/cpython

    All issues in python/cpython

    Similar issues

    More Python issues

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.