#13357 closed task (fixed)
Release Trac 1.5.3
Reported by: | Ryan J Ollos | Owned by: | Ryan J Ollos |
---|---|---|---|
Priority: | normal | Milestone: | 1.5.3 |
Component: | general | Version: | |
Severity: | normal | Keywords: | release |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
This ticket is used to coordinate the finalization and testing of the next development-stable release of Trac, 1.5.3.
Attachments (0)
Change History (11)
comment:1 by , 4 years ago
comment:2 by , 4 years ago
Summary: | Release Trac 1.53 → Release Trac 1.5.3 |
---|
follow-up: 4 comment:3 by , 4 years ago
I don't know if there are good reasons, but I've seen several projects moving metadata to setup.cfg
, like this Genshi change. If nothing else, it's a little cleaner and easier to read and edit.
follow-up: 6 comment:4 by , 4 years ago
Replying to Ryan J Ollos:
I don't know if there are good reasons, but I've seen several projects moving metadata to
setup.cfg
, like this Genshi change. If nothing else, it's a little cleaner and easier to read and edit.
Sounds good.
If using metadata section in setup.cfg, setuptools
in install_requires
should be >=30.3.0
.
refs. https://setuptools.readthedocs.io/en/latest/history.html#v30-3-0
comment:5 by , 4 years ago
We could use python_requires parameter to prevent installing with Python 2.
comment:6 by , 4 years ago
Replying to Jun Omae:
Replying to Ryan J Ollos:
I don't know if there are good reasons, but I've seen several projects moving metadata to
setup.cfg
, like this Genshi change. If nothing else, it's a little cleaner and easier to read and edit.Sounds good.
⇒ #13359
Typo in issue title? :-)