If a value created by Py_VaBuildValue and parameter "b" is transfered - a PyLong_Type value is returned despite of the fact that it would be reasonable if PyBool_Type were returned. Are there any reasons for this?

modsupport.c Ln 214

What makes you think it should be a boolean?
in http://docs.python.org/py3k/c-api/arg.html#Py_BuildValue "b" means "byte" and is processed as a tiny integer.

Now, that's true that Py_BuildValue could have a format for boolean values.  Maybe with a "?" parameter?

Thank you, how is it possible to ask the developers to add such a flag?

This is the right place to ask... but it will be faster if someone provides a patch.

case 'g':
		{
			int n;
			n = va_arg(*p_va, int);

			if (n == 0)
				Py_RETURN_FALSE;
			else
				Py_RETURN_TRUE;
		}

Here's patch against 2.6


--- a/Python/modsupport.c	Tue Aug 24 18:19:58 2010 +0200
+++ b/Python/modsupport.c	Tue Jan 11 23:50:40 2011 +0300
@@ -459,6 +459,16 @@
             return v;
         }
 
+        case '?':
+        {
+            int n;
+            n = va_arg(*p_va, int);
+            if (n == 0)
+                Py_RETURN_FALSE;
+            else
+                Py_RETURN_TRUE;
+        }
+
         case ':':
         case ',':
         case ' ':

Add a boolean format option to Py_BuildValue and Py_VaBuildValue

Also added some tests to test_capi that verifies Py_BuildValue is building the right type. I did not add tests for every possible type as it has lived this long without, but I did want to test my new code.

This test is wrong::
   if (!PyBool_Check(test_var) && test_var == Py_False)
the second part is never executed.
   if (test_var != Py_False)
is enough to test the return value.

+    test_var = Py_BuildValue("?", 0);
+    if (PyBool_Check(test_var) && test_var == Py_True) {
+        PyErr_SetString(TestError, "Failed to Create boolean");
+        return NULL;
+    }
+    
+    test_var = Py_BuildValue("?", 1);
+    if (PyBool_Check(test_var) && test_var == Py_False) {
+        PyErr_SetString(TestError, "Failed to Create boolean");
+        return NULL;
+    }

sorry ^_^

+    test_var = Py_BuildValue("?", 0);
+    if (!PyBool_Check(test_var) || test_var == Py_True) {
+        PyErr_SetString(TestError, "Failed to Create boolean");
+        return NULL;
+    }
+    
+    test_var = Py_BuildValue("?", 1);
+    if (!PyBool_Check(test_var) || test_var == Py_False) {
+        PyErr_SetString(TestError, "Failed to Create boolean");
+        return NULL;
+    }

Correct the tests. They passed before but had a logic flaw that caused them to never test that the correct boolean value was being returned.

Can somebody do a patch review on this please, it's against _testcapimodule.c.

If it's a easy patch, I would like to pick it up. Can someone please explain how should I proceed with this? I am already done with the setup.
TIA

Maybe 'p' as in  https://docs.python.org/3/c-api/arg.html#other-objects ?