Custom Query (132 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (25 - 27 of 132)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Ticket Resolution Summary Owner Reporter
#31 fixed PyYAML for Python 2.5 xi edemaine@…

Reported by edemaine@…, 8 years ago.

Description

Could you compile a Windows binary of PyYAML for Python 2.5 (released fairly recently)? Ideally with libyaml support built in...

#32 fixed patch to make libyaml compile in visual studio xi roel _ dot _ vanhout _ at _ gmail _ dot _ com

Reported by roel _ dot _ vanhout _ at _ gmail _ dot _ com, 8 years ago.

Description

2 issues:

  • pointer arithmetic on void*'s is a gcc-ism. I 'solved' it by casting them all to a unsigned char (typedef'd), I'm not sure if a unsigned char is guaranteed to be the same size as a void* on all architectures - it worked on 32-bit Windows, FWIW.
  • A shorthand struct assignment didn't work, I'm not sure if it's valid C or not but whatever, by writing it out in full it compiled ok.
#33 fixed PyYAML + libyyaml shouldn't need PyRex xi edemaine@…

Reported by edemaine@…, 8 years ago.

Description

In my understanding of PyRex? (which, I admit, is fairly limited), it is a tool that converts PyRex? code into C (.c, .h, etc.) and Python code. Can't this conversion be done ahead of time when assembling a distribution, so that you don't need PyRex? on the install side? (Same as running lex or yacc etc. at distribution time instead of install time.) Or is there something more subtle going on during installation that this is actually necessary?

Reducing the barrier to installation should make the "fast PyYAML solution" (PyYAML + libyaml) more widely available.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Note: See TracQuery for help on using queries.