Package Details: python-graph-tool 2.80-2

Git Clone URL: https://aur.archlinux.org/python-graph-tool.git (read-only, click to copy)
Package Base: python-graph-tool
Description: A Python module for manipulation and statistical analysis of graphs
Upstream URL: https://graph-tool.skewed.de
Keywords: graphs networks science
Licenses: LGPL3
Conflicts: python3-graph-tool
Provides: python3-graph-tool
Replaces: python3-graph-tool
Submitter: muellner
Maintainer: count0
Last Packager: count0
Votes: 29
Popularity: 0.000000
First Submitted: 2013-11-24 19:22 (UTC)
Last Updated: 2024-12-31 10:04 (UTC)

Latest Comments

1 2 3 4 5 6 .. 15 Next › Last »

count0 commented on 2025-01-02 12:33 (UTC)

@lahwaacz That's awesome! Thank you!

I just installed the package and it works fine.

I only noticed a problem with the optimization level used for compilation, and I reported it here: https://gitlab.archlinux.org/archlinux/packaging/packages/python-graph-tool/-/issues/1

lahwaacz commented on 2025-01-02 12:01 (UTC)

@count0 Thanks, I've moved the package with some adjustments: https://gitlab.archlinux.org/archlinux/packaging/packages/python-graph-tool

The binary package is now in extra-testing, please let me know if you find any issues 😊

count0 commented on 2024-12-31 10:06 (UTC)

@lahwaacz that's great news! I've added the LICENSE file. Please let me know if any assistance is needed.

lahwaacz commented on 2024-12-31 09:14 (UTC)

I would like to move this package to the Arch Linux extra repository. Can you add a 0BSD license to this repository (affecting the PKGBUILD) that we need according to RFC 0040?

count0 commented on 2024-07-15 14:36 (UTC)

FYI, the compilation errors below have been fixed for some time upstream.

aeden commented on 2023-09-13 04:21 (UTC)

I got past the compiler error by adding

#include <boost/regex/pending/unicode_iterator.hpp>

to src/graph/gml.hh, directly after #include <boost/spirit/include/support_istream_iterator.hpp>

Someone needs to file a bug report upstream.

aeden commented on 2023-09-13 02:59 (UTC) (edited on 2023-09-13 03:00 (UTC) by aeden)

Could not make package. Compiler errors:

In file included from src/graph/graph_io.cc:40:
src/graph/gml.hh: In function 'bool graph_tool::read_gml(std::istream&, Graph&, boost::dynamic_properties&, const std::unordered_set<std::__cxx11::basic_string<char> >&, const std::unordered_set<std::__cxx11::basic_string<char> >&, const std::unordered_set<std::__cxx11::basic_string<char> >&)':
src/graph/gml.hh:367:5: error: 'u8_to_u32_iterator' was not declared in this scope
  367 |     u8_to_u32_iterator<spirit::istream_iterator> tbegin(begin), tend(end);
      |     ^~~~~~~~~~~~~~~~~~
src/graph/gml.hh:367:48: error: expected primary-expression before '>' token
  367 |     u8_to_u32_iterator<spirit::istream_iterator> tbegin(begin), tend(end);
      |                                                ^
src/graph/gml.hh:367:50: error: there are no arguments to 'tbegin' that depend on a template parameter, so a declaration of 'tbegin' must be available [-fpermissive]
  367 |     u8_to_u32_iterator<spirit::istream_iterator> tbegin(begin), tend(end);
      |                                                  ^~~~~~
src/graph/gml.hh:367:50: note: (if you use '-fpermissive', G++ will accept your code, but allowing the use of an undeclared name is deprecated)
src/graph/gml.hh:367:65: error: there are no arguments to 'tend' that depend on a template parameter, so a declaration of 'tend' must be available [-fpermissive]
  367 |     u8_to_u32_iterator<spirit::istream_iterator> tbegin(begin), tend(end);
      |                                                                 ^~~~
src/graph/gml.hh:370:23: error: 'tbegin' was not declared in this scope; did you mean 'begin'?
  370 |         parse_grammar(tbegin, tend, g, dp,
      |                       ^~~~~~
      |                       begin
src/graph/gml.hh:370:31: error: 'tend' was not declared in this scope; did you mean 'end'?
  370 |         parse_grammar(tbegin, tend, g, dp,
      |                               ^~~~
      |                               end
src/graph/gml.hh: In instantiation of 'bool graph_tool::read_gml(std::istream&, Graph&, boost::dynamic_properties&, const std::unordered_set<std::__cxx11::basic_string<char> >&, const std::unordered_set<std::__cxx11::basic_string<char> >&, const std::unordered_set<std::__cxx11::basic_string<char> >&) [with Graph = boost::adj_list<long unsigned int>; std::istream = std::basic_istream<char>]':
src/graph/graph_io.cc:341:33:   required from here
src/graph/gml.hh:367:56: error: 'tbegin' was not declared in this scope; did you mean 'begin'?
  367 |     u8_to_u32_iterator<spirit::istream_iterator> tbegin(begin), tend(end);
      |                                                  ~~~~~~^~~~~~~
      |                                                  begin
src/graph/gml.hh:367:69: error: 'tend' was not declared in this scope; did you mean 'end'?
  367 |     u8_to_u32_iterator<spirit::istream_iterator> tbegin(begin), tend(end);
      |                                                                 ~~~~^~~~~
      |                                                                 end
make[1]: *** [Makefile:3908: src/graph/graph_io.lo] Error 1

count0 commented on 2022-12-09 13:51 (UTC)

I've incorporated your suggestion, which indeed is enough to prevent the runtime errors.

I've investigated further and found the source of the problem. It's entirely innocuous, and the vector access in question would be completely optimized away if it weren't for the assert itself. 🤦

I've fixed it upstream, but I will keep this fix here, since I don't understand why asserts should be turned on by default in production code. The assert that fails here is evoked in every vector access!!! I'm glad the user got an error instead of a super slow code... Otherwise this performance regression would have passed unnoticed.

lahwaacz commented on 2022-12-09 07:05 (UTC)

@count0 OK, I've got it. In that case, I propose the following which removes the one flag from default /etc/makepkg.conf which triggers the assertions:

# disable assertions which lead to runtime failures
CXXFLAGS=${CXXFLAGS/-Wp,-D_GLIBCXX_ASSERTIONS/}
export CXXFLAGS="$CXXFLAGS -flto=auto -fno-fat-lto-objects"

Those assertion errors still indicate an error, though. Some code in graph-tool or boost-python or something is most likely abusing the STL. Has anyone reported the issue?

jg-you commented on 2022-12-09 02:29 (UTC)

@count0 Thanks for the patch; I just successfully rebuilt from the AUR and do not get STL assertion errors anymore.