On Mon, 26 Sep 2016 at 15:38 Guido van Rossum wrote:
> Thanks for the reality check Trent! I think if enough people with core
> committer bits want to keep supporting Solaris / Illumos / OpenIndiana
> / other variants that's fine, but I don't think that just having some
> VMs to test on is enough
Yeah, that should work. The implementation is something like a byte
offset to the start of a line plus a character count, plus some misc
flags. I found this implementation in the 2.6 code (the last version
where it was pure Python code):
def _pack_cookie(self, position, dec_flags=0,
Ben Leslie wrote:
But the idea of transmitting these offsets outside of a running
process is not something that I had anticipated. It got me thinking:
is there a guarantee that these opaque values returned from tell() is
stable across different versions of Python?
Are they even guaranteed to wo
Thanks for the reality check Trent! I think if enough people with core
committer bits want to keep supporting Solaris / Illumos / OpenIndiana
/ other variants that's fine, but I don't think that just having some
VMs to test on is enough -- we also need people who can fix problems
if those buildbots
I work for Joyent (joyent.com) now, which employs a number of devs that
work on illumos (illumos.org). We also provide cloud infrastructure. Would
it help if we offered one or more instances (VMs) on which to run buildbot
slaves (and on which volunteers for bug fixing could hack)? I know a lot
of
The issue tracker is your friend!
On Mon, Sep 26, 2016 at 5:25 AM, Michael Felt wrote:
>
> On 13/09/2016 02:15, Ned Deily wrote:
>>
>> the challenge is to put the finishing touches on the features and
>> documentation, squash bugs, and test test test. The next preview release
>> will be 3.6.0b2
On 13/09/2016 02:15, Ned Deily wrote:
the challenge is to put the finishing touches on the features and
documentation, squash bugs, and test test test. The next preview release will
be 3.6.0b2
Found one typo in Modules/_io/_iomodule.h on line 156 - #endif^L rather
than #endif (posted as an
On Mon, Sep 26, 2016, at 05:30, Ben Leslie wrote:
> I think the case of JSON or SQL database is even more important though.
>
> tell/seek can return 129-bit integers (maybe even more? my maths might
> be off here).
>
> The very large integers that can be returned by tell() will break
> serializat
It was pointed out in private email that technically JSON can
represent very large integers even if ECMAScript itself can't.
But the idea of transmitting these offsets outside of a running
process is not something that I had anticipated. It got me thinking:
is there a guarantee that these opaque v
I think the case of JSON or SQL database is even more important though.
tell/seek can return 129-bit integers (maybe even more? my maths might
be off here).
The very large integers that can be returned by tell() will break
serialization to JSON, and storing in a SQL database (at least for
most da
On 25 September 2016 at 17:21, MRAB wrote:
> On 2016-09-26 00:21, Ben Leslie wrote:
>>
>> Hi all,
>>
>> I recently shot myself in the foot by assuming that TextIO.tell
>> returned integers rather than opaque cookies. Specifically I was
>> adding an offset to the value returned by TextIO.tell. In r
11 matches
Mail list logo
