Skip to content

release: python-pptx-extended 1.1.0#8

Closed
MHoroszowski wants to merge 1 commit into
masterfrom
release/v1.1.0
Closed

release: python-pptx-extended 1.1.0#8
MHoroszowski wants to merge 1 commit into
masterfrom
release/v1.1.0

Conversation

@MHoroszowski
Copy link
Copy Markdown
Owner

Summary

  • Records the metadata changes for the 1.1.0 release that's already published to PyPI at https://pypi.org/project/python-pptx-extended/1.1.0/.
  • Renames the distribution from python-pptx to python-pptx-extended so the fork can be published (python-pptx is owned by Steve Canny on PyPI). The import name is unchanged (import pptx).
  • Bumps __version__ to 1.1.0, adds a fork notice to README, and a HISTORY entry summarizing the five fork features merged into master prior to release: shadow effects, bullet/numbered lists, table cell borders, line cap/join, line end types.

This PR is a metadata-only change; no library code is touched.

What was actually published

  • sdist: python_pptx_extended-1.1.0.tar.gz
  • wheel: python_pptx_extended-1.1.0-py3-none-any.whl
  • Verified install from real PyPI in a clean venv: import pptx; pptx.__version__ == '1.1.0'; Presentation() instantiates.
  • TestPyPI dry run: https://test.pypi.org/project/python-pptx-extended/1.1.0/

Note on the v1.1.0 git tag

The v1.1.0 tag was pushed to origin immediately after the PyPI upload, but it points at the pre-release commit 14ee64cf rather than this PR's release commit 9a3ab2aa. The wheel on PyPI was built from this PR's tree. Once this PR merges, the tag should be force-updated to point at the merge commit so git checkout v1.1.0 matches the published artifact:

```
git tag -fa v1.1.0 -m "python-pptx-extended 1.1.0"
git push origin v1.1.0 --force
```

Test plan

  • Confirm pyproject.toml name, maintainers, description, and URLs read correctly
  • Confirm __version__ == \"1.1.0\" in src/pptx/init.py
  • Confirm README fork-notice renders on GitHub
  • After merge: re-tag v1.1.0 to the merge commit and force-push the tag

🤖 Generated with Claude Code

Rename distribution to python-pptx-extended for PyPI publication; the
upstream python-pptx name is owned by Steve Canny on PyPI and cannot be
reused. Import name (pptx) is unchanged so user code is unaffected.

- pyproject.toml: name -> python-pptx-extended, add maintainer, fork
  description, fork repo URLs (Upstream URL preserved).
- src/pptx/__init__.py: bump __version__ to 1.1.0.
- README.rst: prepend fork notice listing the five added features and
  the install-conflict caveat with upstream.
- HISTORY.rst: add 1.1.0 (2026-05-01) entry.

Published to PyPI: https://pypi.org/project/python-pptx-extended/1.1.0/

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@MHoroszowski
Copy link
Copy Markdown
Owner Author

Superseded by #9.

The metadata commit 9a3ab2aa from this PR was cherry-picked into feature/customxml as fdde8a43, with the customXml feature added on top and the HISTORY 1.2.0 entry layered above this PR's 1.1.0 entry. The CI failures here were the pyparsing deprecation issue, fixed in #9 by commit 1b53585f.

Closing as redundant. The release/v1.1.0 branch can be deleted after #9 merges — its content is fully represented in feature/customxml.

Note: the v1.1.0 git tag retargeting that this PR's body called out is still pending — it currently points at master's pre-release commit 14ee64cf. After #9 merges, force-update the tag to the merge commit so git checkout v1.1.0 matches the artifact published to PyPI.

MHoroszowski added a commit that referenced this pull request May 5, 2026
feat: customXml support (1.2.0); supersedes #7 and #8
@MHoroszowski MHoroszowski deleted the release/v1.1.0 branch May 5, 2026 17:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant