xvfbwrapper 0.2.33__tar.gz → 0.2.34__tar.gz

{xvfbwrapper-0.2.33/xvfbwrapper.egg-info → xvfbwrapper-0.2.34}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: xvfbwrapper
-Version: 0.2.33
+Version: 0.2.34
 Summary: Manage headless displays with Xvfb (X virtual framebuffer)
 Author: Corey Goldberg
 Maintainer: Corey Goldberg
@@ -63,13 +63,21 @@ See the [module API documentation][api-docs] for more information.
     </td>
   </tr>
   <tr>
-    <td>Build/Tests (CI)</td>
+    <td>Tests (CI)</td>
     <td>
       <a href="https://github.com/cgoldberg/xvfbwrapper/actions/workflows/test.yml">
         <img src="https://github.com/cgoldberg/xvfbwrapper/actions/workflows/test.yml/badge.svg">
       </a>
     </td>
   </tr>
+  <tr>
+    <td>API Docs (CI)</td>
+    <td>
+      <a href="https://github.com/cgoldberg/xvfbwrapper/actions/workflows/docs.yml">
+        <img src="https://github.com/cgoldberg/xvfbwrapper/actions/workflows/docs.yml/badge.svg">
+      </a>
+    </td>
+  </tr>
   <tr>
     <td>Supported Python Versions</td>
     <td>
@@ -217,12 +225,10 @@ xvfb.start()  # Xvfb will be called with the `ttyxx -nocursor +extension RANDR`
 
 #### Multithreaded execution:
 
-To run several Xvfb displays at the same time, you can use the `environ`
-keyword when starting the `Xvfb` instances. This provides isolation between
-processes or threads. Be sure to use the environment dictionary you initialize
-`Xvfb` with in your subsequent calls. Also, if you wish to inherit your current
-environment, you must use the copy method of `os.environ` and not simply
-assign a new variable to `os.environ`:
+To run several Xvfb displays at the same time, you can use the `environ` keyword
+when starting the `Xvfb` instances. This provides isolation between processes or
+threads. If you wish to inherit your current environment, you must use the copy
+method of `os.environ` and not simply assign a new variable to `os.environ`:
 
 ```python
 import os
@@ -285,8 +291,6 @@ if __name__ == "__main__":
 
 ## Development
 
-- Git: [github.com/cgoldberg/xvfbwrapper.git][github-repo]
-
 - Create a virtual env and install required testing packages:
 
     ```

{xvfbwrapper-0.2.33 → xvfbwrapper-0.2.34}/README.md

@@ -32,13 +32,21 @@ See the [module API documentation][api-docs] for more information.
     </td>
   </tr>
   <tr>
-    <td>Build/Tests (CI)</td>
+    <td>Tests (CI)</td>
     <td>
       <a href="https://github.com/cgoldberg/xvfbwrapper/actions/workflows/test.yml">
         <img src="https://github.com/cgoldberg/xvfbwrapper/actions/workflows/test.yml/badge.svg">
       </a>
     </td>
   </tr>
+  <tr>
+    <td>API Docs (CI)</td>
+    <td>
+      <a href="https://github.com/cgoldberg/xvfbwrapper/actions/workflows/docs.yml">
+        <img src="https://github.com/cgoldberg/xvfbwrapper/actions/workflows/docs.yml/badge.svg">
+      </a>
+    </td>
+  </tr>
   <tr>
     <td>Supported Python Versions</td>
     <td>
@@ -186,12 +194,10 @@ xvfb.start()  # Xvfb will be called with the `ttyxx -nocursor +extension RANDR`
 
 #### Multithreaded execution:
 
-To run several Xvfb displays at the same time, you can use the `environ`
-keyword when starting the `Xvfb` instances. This provides isolation between
-processes or threads. Be sure to use the environment dictionary you initialize
-`Xvfb` with in your subsequent calls. Also, if you wish to inherit your current
-environment, you must use the copy method of `os.environ` and not simply
-assign a new variable to `os.environ`:
+To run several Xvfb displays at the same time, you can use the `environ` keyword
+when starting the `Xvfb` instances. This provides isolation between processes or
+threads. If you wish to inherit your current environment, you must use the copy
+method of `os.environ` and not simply assign a new variable to `os.environ`:
 
 ```python
 import os
@@ -254,8 +260,6 @@ if __name__ == "__main__":
 
 ## Development
 
-- Git: [github.com/cgoldberg/xvfbwrapper.git][github-repo]
-
 - Create a virtual env and install required testing packages:
 
     ```

{xvfbwrapper-0.2.33 → xvfbwrapper-0.2.34}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "xvfbwrapper"
-version = "0.2.33"
+version = "0.2.34"
 description = "Manage headless displays with Xvfb (X virtual framebuffer)"
 license = "MIT"
 license-files = ["LICENSE"]
@@ -63,6 +63,7 @@ py-modules = ["xvfbwrapper"]
 
 [tool.pytest]
 addopts = ["-v"]
+filterwarnings = ["default"]
 
 [tool.ruff]
 line-length = 88

{xvfbwrapper-0.2.33 → xvfbwrapper-0.2.34}/test_xvfb.py

@@ -6,7 +6,6 @@
 
 import os
 import re
-import sys
 import tempfile
 import unittest
 from contextlib import suppress
@@ -206,8 +205,7 @@ class TestXvfb(XvfbCleanTestCase):
         unwriteable_dir = "/etc"
         xvfb = Xvfb(tempdir=unwriteable_dir)
         with self.assertRaisesRegex(
-            RuntimeError,
-            f"Could not access writable temp directory: {unwriteable_dir}",
+            RuntimeError, f"Could not access writable temp directory: {unwriteable_dir}"
         ):
             xvfb.start()
         self.assertIsNone(xvfb.proc)
@@ -216,8 +214,7 @@ class TestXvfb(XvfbCleanTestCase):
         unknown_dir = "/tmp/some_unknown_path"
         xvfb = Xvfb(tempdir=unknown_dir)
         with self.assertRaisesRegex(
-            RuntimeError,
-            f"Could not access writable temp directory: {unknown_dir}",
+            RuntimeError, f"Could not access writable temp directory: {unknown_dir}"
         ):
             xvfb.start()
         self.assertIsNone(xvfb.proc)
@@ -258,8 +255,7 @@ class TestXvfb(XvfbCleanTestCase):
         self.assertEqual(xvfb.new_display, display_num)
         self.assertIsNotNone(xvfb.proc)
         with self.assertRaisesRegex(
-            RuntimeError,
-            f"Could not lock display: {display_num}",
+            RuntimeError, f"Could not lock display: {display_num}"
         ):
             xvfb2.start()
 
@@ -303,8 +299,7 @@ class TestXvfb(XvfbCleanTestCase):
             "bar",
         ]
         with self.assertRaisesRegex(
-            RuntimeError,
-            f"Xvfb display did not open: {expected_cmd_args}",
+            RuntimeError, f"Xvfb display did not open: {expected_cmd_args}"
         ):
             xvfb.start()
         self.assertIsNone(xvfb.proc)
@@ -314,8 +309,7 @@ class TestXvfb(XvfbCleanTestCase):
         self.addCleanup(xvfb.stop)
         xvfb.start()
         with self.assertRaisesRegex(
-            RuntimeError,
-            re.escape(f"Xvfb is already running (PID: {xvfb.proc.pid})"),
+            RuntimeError, re.escape(f"Xvfb is already running (PID: {xvfb.proc.pid})")
         ):
             xvfb.start()
         self.assertIsNotNone(xvfb.proc)
@@ -342,21 +336,10 @@ class TestXvfb(XvfbCleanTestCase):
         with patch("xvfbwrapper.randint", side_effect=side_effect) as mockrandint:
             self.assertEqual(xvfb._get_next_unused_display(), 11)
             self.assertEqual(mockrandint.call_count, 1)
-            if sys.implementation.name == "cpython":
-                # ResourceWarning is only raised on CPython because
-                # of an implementation detail in it's garbage collector.
-                # This does not occur on other Python implementations
-                # (like PyPy).
-                with self.assertWarns(ResourceWarning):
-                    self.assertEqual(xvfb2._get_next_unused_display(), 22)
-                    self.assertEqual(mockrandint.call_count, 3)
-                    self.assertEqual(xvfb3._get_next_unused_display(), 33)
-                    self.assertEqual(mockrandint.call_count, 10)
-            else:
-                self.assertEqual(xvfb2._get_next_unused_display(), 22)
-                self.assertEqual(mockrandint.call_count, 3)
-                self.assertEqual(xvfb3._get_next_unused_display(), 33)
-                self.assertEqual(mockrandint.call_count, 10)
+            self.assertEqual(xvfb2._get_next_unused_display(), 22)
+            self.assertEqual(mockrandint.call_count, 3)
+            self.assertEqual(xvfb3._get_next_unused_display(), 33)
+            self.assertEqual(mockrandint.call_count, 10)
 
     def test_environ_keyword_isolates_environment_modification(self):
         # Check that start and stop methods modified the environ dict if
@@ -380,10 +363,7 @@ class TestXvfb(XvfbCleanTestCase):
         self.addCleanup(xvfb.stop)
         xvfb.start()
         proc = psutil.Process(xvfb.proc.pid)
-        self.assertEqual(
-            proc.environ().get("XVFBWRAPPER_TEST_MARKER"),
-            marker_value,
-        )
+        self.assertEqual(proc.environ().get("XVFBWRAPPER_TEST_MARKER"), marker_value)
 
     def test_start_failure_without_initial_display_env(self):
         # Provide a custom env *without* DISPLAY so orig_display_var == None
@@ -404,8 +384,7 @@ class TestXvfb(XvfbCleanTestCase):
         with (
             patch.object(xvfb, "_local_display_exists", return_value=False),
             self.assertRaisesRegex(
-                RuntimeError,
-                f"Xvfb display did not open: {expected_cmd_args}",
+                RuntimeError, f"Xvfb display did not open: {expected_cmd_args}"
             ),
         ):
             xvfb.start()

{xvfbwrapper-0.2.33 → xvfbwrapper-0.2.34/xvfbwrapper.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: xvfbwrapper
-Version: 0.2.33
+Version: 0.2.34
 Summary: Manage headless displays with Xvfb (X virtual framebuffer)
 Author: Corey Goldberg
 Maintainer: Corey Goldberg
@@ -63,13 +63,21 @@ See the [module API documentation][api-docs] for more information.
     </td>
   </tr>
   <tr>
-    <td>Build/Tests (CI)</td>
+    <td>Tests (CI)</td>
     <td>
       <a href="https://github.com/cgoldberg/xvfbwrapper/actions/workflows/test.yml">
         <img src="https://github.com/cgoldberg/xvfbwrapper/actions/workflows/test.yml/badge.svg">
       </a>
     </td>
   </tr>
+  <tr>
+    <td>API Docs (CI)</td>
+    <td>
+      <a href="https://github.com/cgoldberg/xvfbwrapper/actions/workflows/docs.yml">
+        <img src="https://github.com/cgoldberg/xvfbwrapper/actions/workflows/docs.yml/badge.svg">
+      </a>
+    </td>
+  </tr>
   <tr>
     <td>Supported Python Versions</td>
     <td>
@@ -217,12 +225,10 @@ xvfb.start()  # Xvfb will be called with the `ttyxx -nocursor +extension RANDR`
 
 #### Multithreaded execution:
 
-To run several Xvfb displays at the same time, you can use the `environ`
-keyword when starting the `Xvfb` instances. This provides isolation between
-processes or threads. Be sure to use the environment dictionary you initialize
-`Xvfb` with in your subsequent calls. Also, if you wish to inherit your current
-environment, you must use the copy method of `os.environ` and not simply
-assign a new variable to `os.environ`:
+To run several Xvfb displays at the same time, you can use the `environ` keyword
+when starting the `Xvfb` instances. This provides isolation between processes or
+threads. If you wish to inherit your current environment, you must use the copy
+method of `os.environ` and not simply assign a new variable to `os.environ`:
 
 ```python
 import os
@@ -285,8 +291,6 @@ if __name__ == "__main__":
 
 ## Development
 
-- Git: [github.com/cgoldberg/xvfbwrapper.git][github-repo]
-
 - Create a virtual env and install required testing packages:
 
     ```

{xvfbwrapper-0.2.33 → xvfbwrapper-0.2.34}/xvfbwrapper.py

@@ -195,16 +195,17 @@ class Xvfb:
         """
         tempfile_path = Path(self._tempdir, f".X{display}-lock")
         try:
-            self._lock_display_file = tempfile_path.open("w")
+            lock_file = tempfile_path.open("w")
         except PermissionError:
             return False
+        try:
+            fcntl.flock(lock_file, fcntl.LOCK_EX | fcntl.LOCK_NB)
+        except BlockingIOError:
+            lock_file.close()
+            return False
         else:
-            try:
-                fcntl.flock(self._lock_display_file, fcntl.LOCK_EX | fcntl.LOCK_NB)
-            except BlockingIOError:
-                return False
-            else:
-                return True
+            self._lock_display_file = lock_file
+            return True
 
     def _get_next_unused_display(self) -> int:
         """Randomly choose a display number and try to acquire a lock for it.