Skip to content
GitLab
  1. 21 Dec, 2007 1 commit
    • Tiago Peixoto's avatar
      Directory restructuring of graph_tool Python module (now a package) · 4a7da8a9
      Tiago Peixoto authored 
      Everything was moved into the graph_tool directory, which should have,
after installation, the following structure:

graph_tool/                          Top-level package
      __init__.py                    Initialize the graph_tool package
      libgraph_tool.so               libgraph_tool submodule
      libgraph_tool.la               libtool file for libgraph_tool
      include/                       C++ include files for dynamically
                                     compiled code
      4a7da8a9
  3. 07 Oct, 2007 1 commit
    • Tiago Peixoto's avatar
      Complete overhaul of command line parsing, and support for loading graph-tool... · cb61cc74
      Tiago Peixoto authored 
      Complete overhaul of command line parsing, and support for loading graph-tool as whole as a python module
    
The command line parsing was completely rewritten. It now supports
better parsing of sub-options, with type checking and grouping
support. Error reporting was also significantly improved, and it now
warns of invalid options and option values, before the option is
executed. Some syntax has changed, such as range filtering:
--[vertex|edge]-range-filter was replaced by
--exclude-[vertex|edge]-range and --keep-[vertex|edge]-range, which
should have a clearer meaning. Ranges can also be specified now by
comparison operators (>,<,>=,<=,=), such as ">=10", to indicate a
range of (10, inf). In addition, ranges can now be easily open or
closed at either end, by suffixing the specific end with '*', to
indicate it is closed, ex: "10 700*" means (10,700].
    
The graph-tool script can now be loaded as a python module (it must be
renamed first to 'something.py'). All the command line options (except
'for' and 'history' which become irrelevant) are available as
functions, with full description and optional parameter support. In
addition, pure function objects can be given as parameters where
expressions are asked, instead of strings and files, which enables
convenient extension of graph-tool.
      cb61cc74
  5. 04 Oct, 2007 1 commit
    • Tiago Peixoto's avatar
      · 8e962092
      Tiago Peixoto authored 
      Simplify range filtering, and definitely remove python filtering
    
Simplify range filtering of vertices and edges, by always filtering
both at once, even if all vertices or edges are being considered. This
severely reduces compilation time and memory, at a small potential
cost in run-time speed, which will probably be overshadowed by other
things, such as dynamic_map look-ups ("premature optimization is the
root of all evil"). Also, remove python-filtering, since, in the end,
it is just code bloat, since it is quite slow for most uses and can be
replaced, generally, by python property editing + range filtering.
      8e962092
  7. 12 Sep, 2007 1 commit
  9. 31 Jul, 2007 1 commit
  11. 05 Jul, 2007 2 commits
  13. 02 Jul, 2007 2 commits
  15. 15 Jun, 2007 1 commit
  17. 18 May, 2007 1 commit
  19. 17 May, 2007 1 commit
  21. 16 May, 2007 2 commits
  23. 06 May, 2007 1 commit
  25. 05 May, 2007 3 commits
  27. 29 Jan, 2007 1 commit
  29. 27 Jan, 2007 2 commits
  31. 25 Jan, 2007 1 commit
  33. 09 Aug, 2006 1 commit
  35. 03 Aug, 2006 3 commits
  37. 10 Jul, 2006 1 commit