the table of contents in epub file is too long

Open
#57,491 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Domain
documentation

Research direction

No file, test, or entry point is named in the issue. Start by locating the documentation build path that generates the EPUB table of contents, then determine how its current length is produced and what shorter structure is expected. Done should mean the EPUB table of contents is acceptably shorter without losing necessary navigation.

Written by the indexing model from the issue text.

Description

docs type-feature
BPO 13282
Nosy @birkenfeld, @ezio-melotti, @merwok, @willingc, @JulienPalard, @jcrben

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 2011-10-28.10:08:26.173>
labels = ['3.8', 'type-feature', '3.7', 'docs']
title = 'the table of contents in epub file is too long'
updated_at = <Date 2019-04-11.07:05:55.502>
user = 'https://bugs.python.org/wrobell'

bugs.python.org fields:

activity = <Date 2019-04-11.07:05:55.502>
actor = 'jcrben'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2011-10-28.10:08:26.173>
creator = 'wrobell'
dependencies = []
files = []
hgrepos = []
issue_num = 13282
keywords = []
message_count = 3.0
messages = ['146548', '147477', '339931']
nosy_count = 8.0
nosy_names = ['georg.brandl', 'wrobell', 'ezio.melotti', 'eric.araujo', 'docs@python', 'willingc', 'mdk', 'jcrben']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue13282'
versions = ['Python 3.7', 'Python 3.8']

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.