You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.rst
+52-15Lines changed: 52 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,16 +3,22 @@ Neo4j Bolt Driver for Python
3
3
****************************
4
4
5
5
This repository contains the official Neo4j driver for Python.
6
-
Each driver release (from 4.0 upwards) is built specifically to work with a corresponding Neo4j release, i.e. that with the same ``major.minor`` version number.
7
-
These drivers will also be compatible with the previous Neo4j release, although new server features will not be available.
6
+
Each driver release (from 5.0 upwards) is built specifically to work with a
7
+
corresponding Neo4j release, i.e. that with the same ``major.minor`` version
8
+
number.
9
+
Only the latest ``major.minor`` release of each ``major`` driver series
10
+
receives patches and support.
11
+
These drivers will also be compatible with the previous Neo4j LTS release as
12
+
well as the very next release, although only the common set of features
13
+
between the chosen driver and server versions will be available.
14
+
15
+
See `Version Compatibility`_ for a compatibility matrix.
8
16
9
17
+ Python 3.10 supported.
10
18
+ Python 3.9 supported.
11
19
+ Python 3.8 supported.
12
20
+ Python 3.7 supported.
13
21
14
-
Python 2.7 support has been dropped as of the Neo4j 4.0 release.
+ The driver’s default configuration for encrypted is now false (meaning that driver will only attempt plain text connections by default).
66
+
+ The driver’s default configuration for encrypted is now false
67
+
(meaning that driver will only attempt plain text connections by default).
61
68
62
-
+ Connections to encrypted services (such as Neo4j Aura) should now explicitly be set to encrypted.
69
+
+ Connections to encrypted services (such as Neo4j Aura) should now explicitly
70
+
be set to encrypted.
63
71
64
-
+ When encryption is explicitly enabled, the default trust mode is to trust the CAs that are trusted by operating system and use hostname verification.
72
+
+ When encryption is explicitly enabled, the default trust mode is to trust the
73
+
CAs that are trusted by operating system and use hostname verification.
65
74
66
-
+ This means that encrypted connections to servers holding self-signed certificates will now fail on certificate verification by default.
75
+
+ This means that encrypted connections to servers holding self-signed
76
+
certificates will now fail on certificate verification by default.
67
77
68
78
+ Using the new ``neo4j+ssc`` scheme will allow to connect to servers holding self-signed certificates and not use hostname verification.
69
79
@@ -77,8 +87,8 @@ See, https://neo4j.com/docs/migration-guide/4.0/upgrade-driver/#upgrade-driver-b
77
87
See, https://neo4j.com/docs/driver-manual/current/client-applications/#driver-connection-uris for changes in default security settings between 3.x and 4.x
78
88
79
89
80
-
Connecting with Python Driver 4.x to Neo4j 3.5
81
-
----------------------------------------------
90
+
Connecting with Python Driver 4.x to Neo4j 3.5 (EOL)
0 commit comments