Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The underscore prefix largely means the same thing in the C API as in normal Python: "this function is an implementation detail subject to change, so watch yourself if you use it". You're not forbidden to use such functions, and if it's the only way to achieve a particular goal (e.g. significant efficiency gains in your case), then it's fine to use the API as long as you are aware of the hazard.</p> <p>If the <code>_PyLong_FromByteArray</code> API was truly private, it would be a <code>static</code> function and wouldn't be fully documented and exported in <code>longobject.h</code>. In fact, Tim Peters (a well-known Python core developer) explicitly <a href="http://mail.python.org/pipermail/python-list/2006-August/372368.html" rel="noreferrer">blesses its use</a>:</p> <blockquote> <p>[Dan Christensen]</p> <blockquote> <p>My student and I are writing a C extension that produces a large integer in binary which we'd like to convert to a python long. The number of bits can be a lot more than 32 or even 64. My student found the function _PyLong_FromByteArray in longobject.h which is exactly what we need, but the leading underscore makes me wary. Is it safe to use this function?</p> </blockquote> <p>Python uses it internally, so it better be ;-)</p> <blockquote> <p>Will it continue to exist in future versions of python?</p> </blockquote> <p>No guarantees, and that's why it has a leading underscore: it's not an officially supported, externally documented, part of the advertised Python/C API. It so happens that I added that function, because Python needed some form of its functionality internally across different C modules. Making it an official part of the Python/C API would have been a lot more work (which I didn't have time for), and created an eternal new maintenance burden (which I'm not keen on regardless ;-)).</p> <p>In practice, few people touch this part of Python's implementation, so I don't /expect/ it will go away, or even change, for years to come. The biggest insecurity I can think of offhand is that someone may launch a crusade to make some other byte-array &lt;-> long interface "official" based on a different way of representing negative integers. But even then I expect the current unofficial functions to remain, since the 256's-complement representation remains necessary for the <code>struct</code> module's "q" format, and for the <code>pickle</code> module's protocol=2 long serialization format.</p> <blockquote> <p>Or is there some other method we should use?</p> </blockquote> <p>No. That's why these functions were invented to begin with ;-)</p> </blockquote> <p>Here's the documentation (from Python 3.2.1):</p> <pre class="lang-c prettyprint-override"><code>/* _PyLong_FromByteArray: View the n unsigned bytes as a binary integer in base 256, and return a Python long with the same numeric value. If n is 0, the integer is 0. Else: If little_endian is 1/true, bytes[n-1] is the MSB and bytes[0] the LSB; else (little_endian is 0/false) bytes[0] is the MSB and bytes[n-1] the LSB. If is_signed is 0/false, view the bytes as a non-negative integer. If is_signed is 1/true, view the bytes as a 2's-complement integer, non-negative if bit 0x80 of the MSB is clear, negative if set. Error returns: + Return NULL with the appropriate exception set if there's not enough memory to create the Python long. */ PyAPI_FUNC(PyObject *) _PyLong_FromByteArray( const unsigned char* bytes, size_t n, int little_endian, int is_signed); </code></pre> <p>The main reason it's an "underscore-prefixed" API is because it depends on the implementation of the Python <code>long</code> as an array of words in a power-of-two base. This isn't likely to change, but since you're implementing an API on top of this, you can insulate your callers from changes in the Python API later on.</p>
    singulars
    1. This table or related slice is empty.
    1. POPython extension - construct and inspect large integers efficiently
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USnneonneo
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POPython extension - construct and inspect large integers efficiently
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COVery helpful information about the _PyLong_FromByteArray() approach. Thanks. I would still like to establish if there's a similarly viable approach that is even more direct. I can go via a byte-array (in both directions) but I'd prefer to interact directly with an array of "limbs" - in a way analogous to when using GMP/MPIR - especially when reading large integers in C.
      singulars
      1. PO
      1. USaSteve
    2. CO@aSteve: Not without using an even more private API, I'm afraid. `longintrepr.h` defines `struct _longobject`, and there's a nice big documentation block right above it. The only part which might look strange is `PyObject_VAR_HEAD`, which is [well documented](http://docs.python.org/release/3.0/c-api/structures.html#PyObject_VAR_HEAD). Of course, if you actually use `longintrepr.h`, you're responsible for keeping up with any and all API breakage that may result.
      singulars
      1. PO
      1. USnneonneo
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload