Reinstating previously failing test.

Author: scott-griffiths

README.md

@@ -106,4 +106,4 @@ Array('uint7', [45, 100, 15, 1])
 ```
 
 
-<sub>Copyright (c) 2006 - 2025 Scott Griffiths</sub>
+<sub>Copyright (c) 2006 - 2026 Scott Griffiths</sub>

pyproject.toml

@@ -30,7 +30,7 @@ classifiers = [
 keywords = ["binary", "bitarray", "bitvector", "bitfield"]
 dependencies = [
   "bitarray >= 3.0.0, < 4.0",
-  "tibs >= 0.5.5, < 0.6",
+  "tibs >= 0.5.6, < 0.6",
 ]
 
 [project.urls]

release_notes.md

@@ -3,13 +3,13 @@
 
 ### Unreleased: version 4.4.0
 
-This version adds a new optional Rust based backend. This is turned off by default so
+This version adds a new optional Rust-based backend. This is turned off by default so
 shouldn't affect users. The new backend uses the `tibs` library, which is
 by the same author as `bitstring` and should allow some nice optimisations as
 the whole stack can work together.
 
-For now the Rust backend is still 10-20% slower than the C backend (which uses `bitarray`)
-so it's not recommended for general use yet. If you do want to try it then you'll need to
+For now the Rust backend is about the same speed as the C backend (which uses `bitarray`)
+so there are no real advantages to use it yet. If you do want to try it then you'll need to
 set the `BITSTRING_USE_RUST_CORE` environment variable.
 
 ```python
@@ -19,14 +19,15 @@ BITSTRING_USE_RUST_CORE=1 python your_script.py
 You can check which backend is being used using `bitstring.options.using_rust_core` which
 should be `False` unless you've enabled it as detailed above.
 
-The plan is to remove the C backend in a future release once the Rust backend is at least as
-performant, which will allow lots of code simplifications and further performance improvements.
-
-The only other change is explicit support for Python 3.14.
+The plan is to remove the C backend in version 5, which will allow lots of code
+simplifications and further performance improvements.
 
 The `tibs` dependency is a bit experimental and difficult to test on every possible platform.
 If you experience any issues with installation then please file a bug report.
 
+The only other change is explicit support for Python 3.14.
+
+
 ### March 2025: version 4.3.1
 
 * Updated bitarray dependency to allow for v3.x.

tests/test_bitstream.py

@@ -459,23 +459,22 @@ def test_set_slice(self):
         a[-100:-16] = '0x0'
         assert a == '0x0bcde'
 
-    # TODO: Reinstate test - fails for Rust core
-    # def test_inserting_using_set_item(self):
-    #     a = BitStream()
-    #     a[0:0] = '0xdeadbeef'
-    #     assert a == '0xdeadbeef'
-    #     assert a.bytepos == 0
-    #     a[16:16] = '0xfeed'
-    #     assert a == '0xdeadfeedbeef'
-    #     assert a.bytepos == 0
-    #     a[0:0] = '0xa'
-    #     assert a == '0xadeadfeedbeef'
-    #     assert a.bitpos == 0
-    #     a.bytepos = 6
-    #     a[0:8] = '0xff'
-    #     assert a.bytepos == 6
-    #     a[8:0] = '0x000'
-    #     assert a.startswith('0xff000ead')
+    def test_inserting_using_set_item(self):
+        a = BitStream()
+        a[0:0] = '0xdeadbeef'
+        assert a == '0xdeadbeef'
+        assert a.bytepos == 0
+        a[16:16] = '0xfeed'
+        assert a == '0xdeadfeedbeef'
+        assert a.bytepos == 0
+        a[0:0] = '0xa'
+        assert a == '0xadeadfeedbeef'
+        assert a.bitpos == 0
+        a.bytepos = 6
+        a[0:8] = '0xff'
+        assert a.bytepos == 6
+        a[8:0] = '0x000'
+        assert a.startswith('0xff000ead')
 
     def test_slice_assignment_bit_pos(self):
         a = BitStream('int:64=-1')