Updated MSRV info/workflow since it seems 'bitflags', a dependency of 'clap', is now locked at MSRV 1.46

Author: Andrew J Westlake

.github/workflows/ci.yml

@@ -94,10 +94,10 @@ jobs:
       - name: Build (no features)
         run: cargo build --no-default-features --verbose --target ${{ matrix.platform.rust-target }}
 
-      # Omit async-std-runtime feature for MSRV 1.45.0
+      # Omit async-std-runtime and testing features from MSRV 1.45.0 (See README for details)
       - if: matrix.rust == '1.45.0'
         name: Prepare 1.45.0 features
-        run: echo features=testing,attributes,tokio-runtime >> $GITHUB_ENV
+        run: echo features=attributes,tokio-runtime >> $GITHUB_ENV
 
       # Use all features for MSRV 1.46.0 and above
       - if: matrix.rust != '1.45.0'

README.md

@@ -622,6 +622,7 @@ __Before you get started, I personally recommend taking a look at [Event Loop Re
 This library can give spurious failures during finalization prior to PyO3 release `v0.13.2`. Make sure your PyO3 dependency is up-to-date!
 
 ## MSRV
-Currently the MSRV for this library is 1.46.0, _but_ if you don't need to use the `async-std-runtime`
-feature, you can use rust 1.45.0. 
+Currently the MSRV for this library is 1.46.0, _but_ if you don't need to use the `async-std-runtime` 
+or `testing` features, you can still use rust 1.45.0. 
 > `async-std` depends on `socket2` which fails to compile under 1.45.0.
+> `testing` indirectly relies on `bitflags` through `clap`, which is now locked in at MSRV 1.46.0