PKG-INFO 12 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337
  1. Metadata-Version: 1.1
  2. Name: modulegraph
  3. Version: 0.12.1
  4. Summary: Python module dependency analysis tool
  5. Home-page: http://bitbucket.org/ronaldoussoren/modulegraph
  6. Author: Ronald Oussoren
  7. Author-email: ronaldoussoren@mac.com
  8. License: MIT
  9. Download-URL: http://pypi.python.org/pypi/modulegraph
  10. Description: modulegraph determines a dependency graph between Python modules primarily
  11. by bytecode analysis for import statements.
  12. modulegraph uses similar methods to modulefinder from the standard library,
  13. but uses a more flexible internal representation, has more extensive
  14. knowledge of special cases, and is extensible.
  15. Release history
  16. ===============
  17. 0.12.1
  18. ------
  19. * Issue #25: Complex python files could cause an "maximum recursion depth exceeded"
  20. exception due to using stack-based recursion to walk the module AST.
  21. 0.12
  22. ----
  23. * Added 'modulegraph.modulegraph.InvalidSourceModule'. This graph node is
  24. used for Python source modules that cannot be compiled (for example because
  25. they contain syntax errors).
  26. This is primarily useful for being able to create a graph for packages
  27. that have python 2.x or python 3.x compatibility in separate modules that
  28. contain code that isn't valid in the "other" python version.
  29. * Added 'modulegraph.modulegraph.InvalidCompiledModule'. This graph node
  30. is used for Python bytecode modules that cannot be loaded.
  31. * Added 'modulegraph.modulegraph.NamespacePackage'.
  32. Patch by bitbucket user htgoebel.
  33. * No longer add a MissingModule node to the graph for 'collections.defaultdict'
  34. when using 'from collections import defaultdict' ('collections.defaultdict'
  35. is an attribute of 'collections', not a submodule).
  36. * Fixed typo in ModuleGraph.getReferences()
  37. * Added ModuleGraph.getReferers(tonode). This methods yields the
  38. nodes that are referencing *tonode* (the reverse of getReferences)
  39. * The graph will no longer contain MissingModule nodes when using 'from ... import name' to
  40. import a global variable in a python module.
  41. There will still be MissingModule nodes for global variables in C extentions, and
  42. for 'from missing import name' when 'missing' is itself a MissingModule.
  43. * Issue #18: Don't assume that a PEP 302 loader object has a ``path`` attribute. That
  44. attribute is not documented and is not always present.
  45. 0.11.2
  46. ------
  47. *
  48. 0.11.1
  49. ------
  50. * Issue #145: Don't exclude the platform specific 'path' modules (like ntpath)
  51. 0.11
  52. ----
  53. This is a feature release
  54. Features
  55. ........
  56. * Hardcode knowlegde about the compatibility aliases in the email
  57. module (for python 2.5 upto 3.0).
  58. This makes it possible to remove a heavy-handed recipe from py2app.
  59. * Added ``modegraph.zipio.getmode`` to fetch the Unix file mode
  60. for a file.
  61. * Added some handy methods to ``modulegraph.modulegraph.ModuleGraph``.
  62. 0.10.5
  63. ------
  64. This is a bugfix release
  65. * Don't look at the file extension to determine the file type
  66. in modulegraph.find_modules.parse_mf_results, but use the
  67. class of the item.
  68. * Issue #13: Improved handing of bad relative imports
  69. ("from .foo import bar"), these tended to raise confusing errors and
  70. are now handled like any other failed import.
  71. 0.10.4
  72. ------
  73. This is a bugfix release
  74. * There were no 'classifiers' in the package metadata due to a bug
  75. in setup.py.
  76. 0.10.3
  77. ------
  78. This is a bugfix release
  79. Bugfixes
  80. ........
  81. * ``modulegraph.find.modules.parse_mf_results`` failed when the main script of
  82. a py2app module didn't have a file name ending in '.py'.
  83. 0.10.2
  84. ------
  85. This is a bugfix release
  86. Bugfixes
  87. ........
  88. * Issue #12: modulegraph would sometimes find the wrong package *__init__*
  89. module due to using the wrong search method. One easy way to reproduce the
  90. problem was to have a toplevel module named *__init__*.
  91. Reported by Kentzo.
  92. 0.10.1
  93. ------
  94. This is a bugfix release
  95. Bugfixes
  96. ........
  97. * Issue #11: creating xrefs and dotty graphs from modulegraphs (the --xref
  98. and --graph options of py2app) didn't work with python 3 due to use of
  99. APIs that aren't available in that version of python.
  100. Reported by Andrew Barnert.
  101. 0.10
  102. ----
  103. This is a minor feature release
  104. Features
  105. ........
  106. * ``modulegraph.find_modules.find_needed_modules`` claimed to automaticly
  107. include subpackages for the "packages" argument as well, but that code
  108. didn't work at all.
  109. * Issue #9: The modulegraph script is deprecated, use
  110. "python -mmodulegraph" instead.
  111. * Issue #10: Ensure that the result of "zipio.open" can be used
  112. in a with statement (that is, ``with zipio.open(...) as fp``.
  113. * No longer use "2to3" to support Python 3.
  114. Because of this modulegraph now supports Python 2.6
  115. and later.
  116. * Slightly improved HTML output, which makes it easier
  117. to manipulate the generated HTML using JavaScript.
  118. Patch by anatoly techtonik.
  119. * Ensure modulegraph works with changes introduced after
  120. Python 3.3b1.
  121. * Implement support for PEP 420 ("Implicit namespace packages")
  122. in Python 3.3.
  123. * ``modulegraph.util.imp_walk`` is deprecated and will be
  124. removed in the next release of this package.
  125. Bugfixes
  126. ........
  127. * The module graph was incomplete, and generated incorrect warnings
  128. along the way, when a subpackage contained import statements for
  129. submodules.
  130. An example of this is ``sqlalchemy.util``, the ``__init__.py`` file
  131. for this package contains imports of modules in that modules using
  132. the classic relative import syntax (that is ``import compat`` to
  133. import ``sqlalchemy.util.compat``). Until this release modulegraph
  134. searched the wrong path to locate these modules (and hence failed
  135. to find them).
  136. 0.9.2
  137. -----
  138. This is a bugfix release
  139. Bugfixes
  140. ........
  141. * The 'packages' option to modulegraph.find_modules.find_modules ignored
  142. the search path argument but always used the default search path.
  143. * The 'imp_find_modules' function in modulegraph.util has an argument 'path',
  144. this was a string in previous release and can now also be a sequence.
  145. * Don't crash when a module on the 'includes' list doesn't exist, but warn
  146. just like for missing 'packages' (modulegraph.find_modules.find_modules)
  147. 0.9.1
  148. -----
  149. This is a bugfix release
  150. Bug fixes
  151. .........
  152. - Fixed the name of nodes imports in packages where the first element of
  153. a dotted name can be found but the rest cannot. This used to create
  154. a MissingModule node for the dotted name in the global namespace instead
  155. of relative to the package.
  156. That is, given a package "pkg" with submodule "sub" if the "__init__.py"
  157. of "pkg" contains "import sub.nomod" we now create a MissingModule node
  158. for "pkg.sub.nomod" instead of "sub.nomod".
  159. This fixes an issue with including the crcmod package in application
  160. bundles, first reported on the pythonmac-sig mailinglist by
  161. Brendan Simon.
  162. 0.9
  163. ---
  164. This is a minor feature release
  165. Features:
  166. - Documentation is now generated using `sphinx <http://pypi.python.org/pypi/sphinx>`_
  167. and can be viewed at <http://packages.python.org/modulegraph>.
  168. The documention is very rough at this moment and in need of reorganisation and
  169. language cleanup. I've basiclly writting the current version by reading the code
  170. and documenting what it does, the order in which classes and methods are document
  171. is therefore not necessarily the most useful.
  172. - The repository has moved to bitbucket
  173. - Renamed ``modulegraph.modulegraph.AddPackagePath`` to ``addPackagePath``,
  174. likewise ``ReplacePackage`` is now ``replacePackage``. The old name is still
  175. available, but is deprecated and will be removed before the 1.0 release.
  176. - ``modulegraph.modulegraph`` contains two node types that are unused and
  177. have unclear semantics: ``FlatPackage`` and ``ArchiveModule``. These node
  178. types are deprecated and will be removed before 1.0 is released.
  179. - Added a simple commandline tool (``modulegraph``) that will print information
  180. about the dependency graph of a script.
  181. - Added a module (``zipio``) for dealing with paths that may refer to entries
  182. inside zipfiles (such as source paths referring to modules in zipped eggfiles).
  183. With this addition ``modulegraph.modulegraph.os_listdir`` is deprecated and
  184. it will be removed before the 1.0 release.
  185. Bug fixes:
  186. - The ``__cmp__`` method of a Node no longer causes an exception
  187. when the compared-to object is not a Node. Patch by Ivan Kozik.
  188. - Issue #1: The initialiser for ``modulegraph.ModuleGraph`` caused an exception
  189. when an entry on the path (``sys.path``) doesn't actually exist.
  190. Fix by "skurylo", testcase by Ronald.
  191. - The code no longer worked with python 2.5, this release fixes that.
  192. - Due to the switch to mercurial setuptools will no longer include
  193. all required files. Fixed by adding a MANIFEST.in file
  194. - The method for printing a ``.dot`` representation of a ``ModuleGraph``
  195. works again.
  196. 0.8.1
  197. -----
  198. This is a minor feature release
  199. Features:
  200. - ``from __future__ import absolute_import`` is now supported
  201. - Relative imports (``from . import module``) are now supported
  202. - Add support for namespace packages when those are installed
  203. using option ``--single-version-externally-managed`` (part
  204. of setuptools/distribute)
  205. 0.8
  206. ---
  207. This is a minor feature release
  208. Features:
  209. - Initial support for Python 3.x
  210. - It is now possible to run the test suite
  211. using ``python setup.py test``.
  212. (The actual test suite is still fairly minimal though)
  213. Keywords: import,,dependencies
  214. Platform: any
  215. Classifier: Intended Audience :: Developers
  216. Classifier: License :: OSI Approved :: MIT License
  217. Classifier: Programming Language :: Python
  218. Classifier: Programming Language :: Python :: 2
  219. Classifier: Programming Language :: Python :: 2.7
  220. Classifier: Programming Language :: Python :: 3
  221. Classifier: Programming Language :: Python :: 3.3
  222. Classifier: Programming Language :: Python :: 3.4
  223. Classifier: Topic :: Software Development :: Libraries :: Python Modules
  224. Classifier: Topic :: Software Development :: Build Tools