remove EOL python 3.8 from github CI action. Clarify class expose in …

…docs more. Fixes #96

.github/workflows/main-ci.yml

@@ -18,7 +18,7 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        python-version: ['3.8', '3.9', '3.10', '3.11', '3.12']
+        python-version: ['3.9', '3.10', '3.11', '3.12']
 
     steps:
       - name: Checkout source

Pyro5/__init__.py

@@ -4,7 +4,7 @@
 Pyro - Python Remote Objects.  Copyright by Irmen de Jong ([email protected]).
 """
 
-__version__ = "5.15"
+__version__ = "5.16.dev0"
 __author__ = "Irmen de Jong"
 
 

Readme.rst

@@ -35,7 +35,7 @@ New code should use Pyro5 if at all possible.
 Features
 --------
 
-- written in 100% Python so extremely portable, supported on Python 3.8 and newer, and Pypy3
+- written in 100% Python so extremely portable, supported on Python 3.9 and newer, and Pypy3
 - works between different system architectures and operating systems.
 - able to communicate between different Python versions transparently.
 - defaults to a safe serializer (`serpent <https://pypi.python.org/pypi/serpent>`_) that supports many Python data types.

docs/source/changelog.rst

@@ -2,6 +2,12 @@
 Change Log
 **********
 
+**Pyro 5.16**
+
+- removed Python 3.8 from the support list (it is EOL). Now supported on Python 3.9 or newer.
+- docs: clarify @expose on a class not automatically exposing base class(es).
+
+
 **Pyro 5.15**
 
 - removed Python 3.7 from the support list (it is EOL). Now supported on Python 3.8 or newer.

docs/source/intro.rst

@@ -119,7 +119,7 @@ What has been changed since Pyro4
 
 If you're familiar with Pyro4, most of the things are the same in Pyro5. These are the changes though:
 
-- Supported on Python 3.8 or newer.
+- Supported on Python 3.9 or newer.
 - the Pyro5 API is redesigned and this library is not compatible with Pyro4 code (although everything should be familiar):
 
       - Pyro5 is the new package name

docs/source/servercode.rst

@@ -41,7 +41,10 @@ It lets you mark the following items to be available for remote access:
 - properties (these will be available as remote attributes on the proxy) It's not possible to expose a 'private' property
   (name starting with underscore). You can't expose attributes directly. It is required to provide a @property for them
   and decorate that with ``@expose``, if you want to provide a remotely accessible attribute.
-- classes as a whole (exposing a class has the effect of exposing every nonprivate method and property of the class automatically)
+- classes as a whole (exposing a class has the effect of exposing every nonprivate method and property of the class automatically).
+  *Note*: only the direct members of the class are exposed. If it's part of a class hierarchy, the members of the base class(es) are *not*
+  automatically exposed as well - you'll still have to ``@expose`` those explicitly. This is to avoid making
+  stuff remotely accessible by accident.
 
 Anything that isn't decorated with ``@expose`` is not remotely accessible.
 

tox.ini

@@ -1,5 +1,5 @@
 [tox]
-envlist=py38,py39,py310,py311,py312,pypy3
+envlist=py39,py310,py311,py312,pypy3
 
 [testenv]
 deps=