Deprecate the _boundary parameter

[nathanncohen]

From the documentation (Graph.get_boundary? or Graph.set_boundary?) there is just no way to know what it does. So because of that probably nobody uses it. Or they guessed the purpose in some way I can't guess myself.

Then there are things like linear-time operations in functions like .delete_vertex (noticed by #15278).

self._boundary = [v for v in self._boundary if v != vertex]

Sooooooooo unless somebody complains and is willing to write some documentation for this parameter, I think it'd be nice to deprecate then remove it.

Nathan

CC: @simon-king-jena

Component: graph theory

Author: Nathann Cohen

Branch/Commit: 8bb60b3

Reviewer: Frédéric Chapoton, Vincent Delecroix

Issue created by migration from https://trac.sagemath.org/ticket/15494

[nathanncohen]

Branch: u/ncohen/15494

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

[065181c](https://github.com/sagemath/sagetrac-mirror/commit/065181c)

trac #15494: Deprecate the graph "boundary" parameter

[sagetrac-git]

Commit: 065181c

[sagetrac-git]

Changed commit from 065181c to 31a301e

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

[31a301e](https://github.com/sagemath/sagetrac-mirror/commit/31a301e)

trac #15494: Deprecate the graph "boundary" parameter

[fchapoton]

comment:5

Hello Nathann,

you should replace all the new doctest:1: (or any other number) by doctest:...: because the numbers will change all the time.

[sagetrac-git]

Changed commit from 31a301e to 8bb60b3

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

c1d7b62	trac #15494: Rebase on 6.2.beta3
8bb60b3	trac #15494: replacing numbers with ...

[nathanncohen]

comment:8

Done

Nathann

[videlec]

comment:10

Hi,

It has been waiting long enough.

Vincent

[videlec]

Reviewer: Frédéric Chapoton, Vincent Delecroix

[vbraun]

Changed branch from u/ncohen/15494 to 8bb60b3