iplotx 1.2.0__tar.gz → 1.2.1__tar.gz

{iplotx-1.2.0 → iplotx-1.2.1}/.github/workflows/test.yml

@@ -12,7 +12,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        python-version: ["3.11", "3.12", "3.13"]
+        python-version: ["3.10", "3.11", "3.12", "3.13"]
 
     steps:
     - uses: actions/checkout@v5

{iplotx-1.2.0 → iplotx-1.2.1}/.gitignore

@@ -179,3 +179,7 @@ cython_debug/
 
 # PyPI configuration file
 .pypirc
+
+# vim backup files
+*.swp
+*.swo

{iplotx-1.2.0 → iplotx-1.2.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: iplotx
-Version: 1.2.0
+Version: 1.2.1
 Summary: Plot networkx from igraph and networkx.
 Project-URL: Homepage, https://github.com/fabilab/iplotx
 Project-URL: Documentation, https://readthedocs.org/iplotx
@@ -26,8 +26,8 @@ Classifier: Programming Language :: Python :: 3.13
 Classifier: Topic :: Scientific/Engineering :: Visualization
 Classifier: Topic :: System :: Networking
 Classifier: Typing :: Typed
-Requires-Python: >=3.11
-Requires-Dist: matplotlib>=2.0.0
+Requires-Python: >=3.10
+Requires-Dist: matplotlib>=3.10.0
 Requires-Dist: numpy>=2.0.0
 Requires-Dist: pandas>=2.0.0
 Provides-Extra: igraph

iplotx-1.2.1/docs/source/code_of_conduct.rst

@@ -0,0 +1,145 @@
+.. _scipy-coc:
+
+ilpotx Code of Conduct
+======================
+
+
+Introduction
+------------
+
+This code of conduct applies to all spaces managed by the iplotx project,
+including all public and private mailing lists, issue trackers, wikis, blogs,
+and any other communication channel used by our community. The iplotx
+project does not organize in-person events, however, events related to our
+community should have a code of conduct similar in spirit to this one.
+
+This code of conduct should be honored by everyone who participates in
+the iplotx community formally or informally, or claims any affiliation with the
+project, in any project-related activities, and, especially, when representing the
+project, in any role.
+
+This code is neither exhaustive nor complete. It serves to distill our common
+understanding of a collaborative, shared environment and goals. Please try to
+follow this code in spirit as much as in letter, to create a friendly and
+productive environment that enriches the surrounding community.
+
+
+Specific guidelines
+-------------------
+
+We strive to:
+
+1. Be open. We invite anyone to participate in our community. We prefer to use
+   public methods of communication for project-related messages, unless
+   discussing something sensitive. This applies to messages for help or
+   project-related support, too; not only is a public-support request much more
+   likely to result in an answer to a question, it also ensures that any
+   inadvertent mistakes in answering are more easily detected and corrected.
+
+2. Be empathetic, welcoming, friendly, and patient. We work together to resolve
+   conflict, and assume good intentions. We may all experience some frustration
+   from time to time, but we do not allow frustration to turn into a personal
+   attack. A community where people feel uncomfortable or threatened is not a
+   productive one.
+
+3. Be collaborative. Our work will be used by other people, and in turn we will
+   depend on the work of others. When we make something for the benefit of the
+   project, we are willing to explain to others how it works, so that they can
+   build on the work to make it even better. Any decision we make will affect
+   users and colleagues, and we take those consequences seriously when making
+   decisions.
+
+4. Be inquisitive. Nobody knows everything! Asking questions early avoids many
+   problems later, so we encourage questions, although we may direct them to
+   the appropriate forum. We will try hard to be responsive and helpful.
+
+5. Be careful in the words that we choose. We are careful and respectful in
+   our communication and we take responsibility for our own speech. Be kind to
+   others. Do not insult or put down other participants. We will not accept
+   harassment or other exclusionary behavior, such as:
+
+  - Violent threats or language directed against another person.
+  - Sexist, racist, or otherwise discriminatory jokes and language.
+  - Posting sexually explicit or violent material.
+  - Posting (or threatening to post) other people's personally identifying information ("doxing").
+  - Sharing private content, such as emails sent privately or non-publicly,
+    or unlogged forums, such as IRC channel history, without the sender's consent.
+  - Personal insults, especially those using racist or sexist terms.
+  - Unwelcome sexual attention.
+  - Excessive profanity. Please avoid swearwords; people differ greatly in their sensitivity to swearing.
+  - Repeated harassment of others. In general, if someone asks you to stop, then stop.
+  - Advocating for, or encouraging, any of the above behavior.
+
+
+Diversity statement
+-------------------
+
+The iplotx project welcomes and encourages participation by everyone. We are
+committed to being a community that everyone enjoys being part of. Although
+we may not always be able to accommodate each individual's preferences, we try
+our best to treat everyone kindly.
+
+No matter how you identify yourself or how others perceive you: we welcome you.
+Though no list can hope to be comprehensive, we explicitly honor diversity in:
+age, culture, ethnicity, genotype, gender identity or expression, language,
+national origin, neurotype, phenotype, political beliefs, profession, race,
+religion, sexual orientation, socioeconomic status, subculture and technical
+ability, to the extent that these do not conflict with this code of conduct.
+
+
+Though we welcome people fluent in all languages, iplotx development is
+conducted in English.
+
+Standards for behavior in the iplotx community are detailed in the Code of
+Conduct above. Participants in our community should uphold these standards
+in all their interactions and help others to do so as well (see next section).
+
+
+Reporting guidelines
+--------------------
+
+We know that it is painfully common for internet communication to start at or
+devolve into obvious and flagrant abuse. We also recognize that sometimes
+people may have a bad day, or be unaware of some of the guidelines in this Code
+of Conduct. Please keep this in mind when deciding on how to respond to a
+breach of this Code.
+
+For clearly intentional breaches, report those to the Code of Conduct committee
+(see below). For possibly unintentional breaches, you may reply to the person
+and point out this Code of Conduct (either in public or in private, whatever is
+most appropriate). If you would prefer not to do that, please feel free to
+report to the Code of Conduct committee directly, or ask the committee for
+advice, in confidence.
+
+You can report issues to the iplotx core developer Fabio Zanini, at
+fabio.zanini@unsw.edu.au.
+
+
+Incident reporting resolution & Code of Conduct enforcement
+-----------------------------------------------------------
+
+We will investigate and respond to all complaints. This Code of Conduct
+Committee  will protect the identity of the reporter, and treat the content
+of complaints as confidential (unless the reporter requests otherwise).
+
+In case of severe and obvious breaches, e.g., personal threat or violent, sexist
+or racist language, we will immediately do our utmost to disconnect the
+originator from iplotx communication channels; please see the manual for details.
+
+In cases not involving clear severe and obvious breaches of this code of
+conduct, the process for acting on any received code of conduct violation
+report will be:
+
+1. Acknowledgement that the report has been received
+2. Reasonable discussion/feedback
+3. Mediation (if feedback didn't help, and only if both reporter and reportee agree to this)
+4. Enforcement via transparent decision by the Code of Conduct Committee
+
+The committee will respond to any report as soon as possible, and at most
+within 72 hours.
+
+
+Endnotes
+--------
+
+This document was adapted from the `SciPy Code of Conduct <https://scipy.github.io/devdocs/dev/conduct/code_of_conduct.html>`_.

{iplotx-1.2.0 → iplotx-1.2.1}/docs/source/index.md

@@ -36,4 +36,5 @@ Plotting API <api/plotting>
 Style API <api/style>
 Artist hierarchy <api/artists>
 Data provider protocols <api/providers>
+Code of conduct <code_of_conduct>
 ```

{iplotx-1.2.0 → iplotx-1.2.1}/iplotx/edge/arrow.py

@@ -2,7 +2,12 @@
 Module for edge arrows in iplotx.
 """
 
-from typing import Never, Optional
+import sys
+if sys.version_info < (3, 11):
+    from typing_extensions import Never
+else:
+    from typing import Never
+from typing import Optional
 
 from math import atan2, cos, sin
 import numpy as np

{iplotx-1.2.0 → iplotx-1.2.1}/iplotx/ingest/__init__.py

@@ -2,16 +2,24 @@
 This module focuses on how to ingest network/tree data into standard data structures no matter what library they come from.
 """
 
-import pathlib
-import pkgutil
-import importlib
-import warnings
+import sys
 from typing import (
     Optional,
     Sequence,
-    Protocol,
 )
+
+# NOTE: __init__ in Protocols has had a difficult gestation
+# https://github.com/python/cpython/issues/88970
+if sys.version_info < (3, 11):
+    Protocol = object
+else:
+    from typing import Protocol
+
 from collections.abc import Hashable
+import pathlib
+import pkgutil
+import importlib
+import warnings
 import pandas as pd
 
 from ..typing import (
@@ -35,6 +43,9 @@ provider_protocols = {
 data_providers: dict[str, dict[str, Protocol]] = {kind: {} for kind in provider_protocols}
 for kind in data_providers:
     providers_path = pathlib.Path(__file__).parent.joinpath("providers").joinpath(kind)
+    if sys.version_info < (3, 11):
+        providers_path = str(providers_path)
+
     for importer, module_name, _ in pkgutil.iter_modules([providers_path]):
         module = importlib.import_module(f"iplotx.ingest.providers.{kind}.{module_name}")
         for key, val in module.__dict__.items():
@@ -138,11 +149,11 @@ def ingest_tree_data(
 
 
 # INTERNAL FUNCTIONS
-def _update_data_providers(kind):
-    """Update data provieders dynamically from external packages."""
+def _update_data_providers(kind: str):
+    """Update data providers dynamically from external packages."""
     discovered_providers = importlib.metadata.entry_points(group=f"iplotx.{kind}_data_providers")
     for entry_point in discovered_providers:
-        if entry_point.name not in data_providers["network"]:
+        if entry_point.name not in data_providers[kind]:
             try:
                 data_providers[kind][entry_point.name] = entry_point.load()
             except Exception as e:

{iplotx-1.2.0 → iplotx-1.2.1}/iplotx/ingest/providers/tree/simple.py

@@ -3,7 +3,6 @@ from typing import (
     Optional,
     Sequence,
     Iterable,
-    Self,
 )
 
 from ...typing import (
@@ -19,12 +18,12 @@ class SimpleTree:
         branch_length: Length of the branch leading to this node/tree.
     """
 
-    children: Sequence[Self] = []
+    children: Sequence = []
     branch_length: float = 1
     name: str = ""
 
     @classmethod
-    def from_dict(cls, data: dict) -> Self:
+    def from_dict(cls, data: dict):
         """Create a SimpleTree from a dictionary.
 
         Parameters:

{iplotx-1.2.0 → iplotx-1.2.1}/iplotx/ingest/typing.py

@@ -5,15 +5,20 @@ Networkx and trees are treated separately for practical reasons: many tree analy
 work as well on general networks.
 """
 
+import sys
 from typing import (
-    NotRequired,
-    TypedDict,
-    Protocol,
     Optional,
     Sequence,
     Any,
     Iterable,
 )
+# NOTE: __init__ in Protocols has had a difficult gestation
+# https://github.com/python/cpython/issues/88970
+if sys.version_info < (3, 11):
+    Protocol = object
+else:
+    from typing import Protocol
+
 from collections.abc import Hashable
 import numpy as np
 import pandas as pd
@@ -26,6 +31,11 @@ from .heuristics import (
     normalise_tree_layout,
 )
 
+if sys.version_info < (3, 11):
+    from typing_extensions import TypedDict, NotRequired
+else:
+    from typing import TypedDict, NotRequired
+
 
 class NetworkData(TypedDict):
     """Network data structure for iplotx."""

{iplotx-1.2.0 → iplotx-1.2.1}/iplotx/network/__init__.py

@@ -1,7 +1,6 @@
 from typing import (
     Optional,
     Sequence,
-    Self,
 )
 import numpy as np
 import pandas as pd
@@ -103,8 +102,8 @@ class NetworkArtist(mpl.artist.Artist):
     @classmethod
     def from_other(
         cls: "NetworkArtist",  # NOTE: This is fixed in Python 3.14
-        other: Self,
-    ) -> Self:
+        other,
+    ):
         """Create a NetworkArtist as a copy of another one.
 
         Parameters:
@@ -123,7 +122,7 @@ class NetworkArtist(mpl.artist.Artist):
     def from_edgecollection(
         cls: "NetworkArtist",  # NOTE: This is fixed in Python 3.14
         edge_collection: EdgeCollection | Edge3DCollection,
-    ) -> Self:
+    ):
         """Create a NetworkArtist from iplotx artists.
 
         Parameters:

{iplotx-1.2.0 → iplotx-1.2.1}/iplotx/version.py

@@ -2,4 +2,4 @@
 iplotx version information module.
 """
 
-__version__ = "1.2.0"
+__version__ = "1.2.1"

{iplotx-1.2.0 → iplotx-1.2.1}/pyproject.toml

@@ -11,11 +11,11 @@ authors = [
 maintainers = [
   {name = "Fabio Zanini", email = "fabio.zanini@unsw.edu.au"}
 ]
-requires-python = ">=3.11"
+requires-python = ">=3.10"
 readme = "README.md"
 dynamic = ["version"]
 dependencies = [
-  "matplotlib>=2.0.0",
+  "matplotlib>=3.10.0",
   "numpy>=2.0.0",
   "pandas>=2.0.0",
 ]