[MERGE] (#183391) improve PyPI integration by adding project metadata to setup.py

[Alexander Belchenko]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Pool пишет:
| On 18/01/2008, John Arbash Meinel <john at arbash-meinel.com> wrote:
|> John Arbash Meinel has voted approve.
|> Status is now: Approved
|> Comment:
|> I'm not sure why we would keep:
|> +version_string = '%d.%d.%d.%s.%d' % version_info
|>
|> Otherwise BB:approve.
|>
|> (I think Alexander wanted to parse the output of 'bzr --version' in an
|> easy and straightforward way, but it has been a while.)
|
| Hi Alexander,
|
| I remember you said something previously about it being easier to
| parse the bzr version number if it was eg 1.1.0.final.0.  I want to
| change the format to make it slightly better integrate with the python
| pypi/distutils standards, so wanted to check this would not be a
| problem for you.

No objections today.

| Are you parsing it from inside python, or in a separate program?  If
| it's inside Python, you can more easily look at bzrlib.version_info,
| which is already a tuple.

It was used in bzr-config utility, i.e. from separate program, because
bzr was invoked as subprocess.
But now development of bzr-config is stopped, because similar functionality
present both in bzr-gtk and QBzr, and they obviously parse version from python
if any.

I just want to point that output of bzr --version should follow version format
and for Python interpreter version too:

C:\>bzr version
Bazaar (bzr) 1.1.0.candidate.1
~  Python interpreter: C:\Program Files\Bazaar\python25.dll 2.5.1.final.0
[...]

Because I like consistency in the output, I suggest to fix formatting of Python
version too.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHkDsfzYr338mxwCURAgiHAKCQ+HYF6FKC8swZVtM9pP0Nh6BD9ACeMLE7
1kJ4nAcX+PuYDXgYez1BHuw=
=L7JS
-----END PGP SIGNATURE-----