./configure: add ability to build and install only shared library (without static libpython3.a)

Open
#75,373 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with the ./configure entry point named in the issue and trace how shared and static Python libraries are selected for building and installation. Done means a configuration can build and install only the shared library without installing static libpython3.a; no test file is identified in the issue.

Written by the indexing model from the issue text.

Description

build
BPO 31190

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 2017-08-12.18:04:09.034>
labels = ['build']
title = './configure: add ability to build and install only shared library (without static libpython3.a)'
updated_at = <Date 2017-08-12.18:04:09.034>
user = 'https://bugs.python.org/dilyanpalauzov'

bugs.python.org fields:

activity = <Date 2017-08-12.18:04:09.034>
actor = 'dilyan.palauzov'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Build']
creation = <Date 2017-08-12.18:04:09.034>
creator = 'dilyan.palauzov'
dependencies = []
files = []
hgrepos = []
issue_num = 31190
keywords = []
message_count = 1.0
messages = ['300206']
nosy_count = 1.0
nosy_names = ['dilyan.palauzov']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue31190'
versions = []

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.