debian/rules, moving generated egg-info directory to unversioned name

[Ben Finney <ben@benfinney.id.au>]

Howdy all,

In several Debian packages of Python software, I've seen an 'install'
target of 'debian/rules' that contains a command similar to this:

=====
install: build
	dh_testdir
	dh_testroot
	dh_installdirs

	$(current_python_version) setup.py install ${DEB_PYTHON_INSTALL_ARGS_ALL}
	mv ${site_packages_dir}/${MODULE_NAME}-${DEB_UPSTREAM_VERSION}-py${CURRENT_PYTHON_VERSION_NUMBER}.egg-info \
		${site_packages_dir}/${MODULE_NAME}.egg-info
=====

This causes, e.g., the egg-info directory 'foo-1.2.3-py2.4.egg-info'
to be moved to 'foo.egg-info'.

Is it a mistake to be dropping the upstream package version string?
Shouldn't this instead be:

=====
[...]
	mv ${site_packages_dir}/${MODULE_NAME}-${DEB_UPSTREAM_VERSION}-py${CURRENT_PYTHON_VERSION_NUMBER}.egg-info \
		${site_packages_dir}/${MODULE_NAME}-${DEB_UPSTREAM_VERSION}.egg-info
=====

resulting in an eventual directory name of 'foo-1.2.3.egg-info', thus
preserving the upstream package version?

-- 
 \        "If it ain't bust don't fix it is a very sound principle and |
  `\      remains so despite the fact that I have slavishly ignored it |
_o__)                                     all my life." —Douglas Adams |
Ben Finney