4 Commits

Author SHA1 Message Date
Christian Berendt
fbe7b3a90c Remove unneeded definitions of Python Source Code Encoding
PEP 0263 (http://legacy.python.org/dev/peps/pep-0263/) is not
used anywhere else and should be removed when it's not needed.

Change-Id: I3f3d56b28001e2b27a4a749ecc9b3ac1c80a5b5c
2014-07-31 13:32:18 +02:00
Christian Berendt
83843c4b57 Bump hacking to version 0.9.2
Change-Id: Id15fb17d6ecb9fbff3dce0105445e78ca5948aee
2014-07-16 15:57:40 +02:00
Joshua Harlow
0326f6781f Fix whitespace that occurs after comma
Use a custom tuple of separators for json.dumps that avoids
having the comma+space, which looks bad if this is ever committed.
Replace it by just having ": " and "," (no space after) instead.

An example of this so that it can be more clear:

http://paste.openstack.org/show/84238/

Note the above paste where the old version has spaces after
commas where as the newer version does not have these spaces.

Change-Id: Ifd04d5e1b26ebdf9db374761f31baaf1e33d87cd
2014-06-16 23:22:45 -07:00
Joshua Harlow
10fb194613 Add a file that can detail the requirements files
From the ML discussion there was a desire to provide
a more detailed version of the requirements that has
information such as license, author... This script
gathers such information from the pypi json API and
writes it to corresponding files that can be used by
automated programs that want to determine this information
without having to go to pypi themselves.

This can be useful for doing requirement license
auditing for example.

To run:

$ python detail.py global-requirements.txt

This will gather the information about the requirements
from pypi (if possible) and then write a new file located
at global-requirements.json with this information.

Change-Id: I710feb7038eec0c916593cce0837823e7f4fce15
2014-03-19 11:44:50 -07:00