Time for v70?

[abravalheri]

There has been some improvements in the last weeks, so I think we should release something before we start compounding more changes.

The major "breaking changes" are related to removal of deprecated code: #4322

I am planning something still this week, beginning of next week max?

[abravalheri]

There is another removal scheduled for next week, so we might as well just wait a bit and do it all at once:

setuptools/setuptools/dep_util.py

Lines 5 to 16 in 2212422

	def __getattr__(name):
	if name not in ['newer_group', 'newer_pairwise_group']:
	raise AttributeError(name)
	SetuptoolsDeprecationWarning.emit(
	"dep_util is Deprecated. Use functions from setuptools.modified instead.",
	"Please use `setuptools.modified` instead of `setuptools.dep_util`.",
	see_url="https://github.com/pypa/setuptools/pull/4069",
	due_date=(2024, 5, 21),
	# Warning added in v69.0.0 on 2023/11/20,
	# See https://github.com/pypa/setuptools/discussions/4128
	)
	return getattr(_modified, name)

Update on #4360.

[jaraco]

Usually, my philosophy is release early and often, as batching changes only complicates triage when there are issues. If we were to release v70 this week and v71 next week, that would increase the churn and bump the number, but it also means that a user with an issue can readily test against those two versions and determine which one (if any) gave them trouble. Maybe they can adopt v70 but not v71. Or maybe neither works, but in either case, they have more information to work with to diagnose and respond.

That said, if #4360 is about to land, I might be tempted to wait, and I have no problem waiting a week if there's nothing pressing that users are waiting on.

[abravalheri]

Understood.

I am thinking of the following:

• We merge Remove deprecated setuptools.dep_util, due date 2024/5/21 #4360
  • breaking change, but other than that, nothing is pending
• Release v70

Then we can:

• Merge Migrated config to pyproject.toml. #4310
  - I have no problem in merging the PR as it is, but it would be nice if we can solve the pending problems before a new release.
• Create a follow-up PR addressing the dynamic aspects, ensuring PEP 621 is followed
• Release v70.1
  • I believe the change to pyproject.toml does not represent a change in APIs.

[jaraco]

#4310 is merged. I seem to think we can live with the dynamic behavior indefinitely (or until someone can prioritize a longer-term fix).