[sage-devel] Re: Py_UNICODE_SIZE on OS X

2008-07-10 Thread William Stein
On Wed, Jul 9, 2008 at 9:04 PM, mabshoff <[EMAIL PROTECTED]> wrote: > > On Jul 9, 8:18 pm, "William Stein" <[EMAIL PROTECTED]> wrote: >> On Wed, Jul 9, 2008 at 8:11 PM, David Philp <[EMAIL PROTECTED]> wrote: > > Hi, > >> > This is a 'for the record' email describing how to use boost.python >> > wi

[sage-devel] Re: Py_UNICODE_SIZE on OS X

2008-07-09 Thread David Philp
On 10/07/2008, at 2:04 PM, mabshoff wrote: >> It should be fine. We used UCS2 until maybe 8 months ago. We >> switched >> as mentioned above only for Linux compatibility. >> >>> You will need to do this for each successive >>> version of sage, which could be tedious. >> >> I would be ok with

[sage-devel] Re: Py_UNICODE_SIZE on OS X

2008-07-09 Thread mabshoff
On Jul 9, 8:18 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > On Wed, Jul 9, 2008 at 8:11 PM, David Philp <[EMAIL PROTECTED]> wrote: Hi, > > This is a 'for the record' email describing how to use boost.python > > with sage on Mac OS X. Thanks to the gentlefolk who walked me through > > it (esp

[sage-devel] Re: Py_UNICODE_SIZE on OS X

2008-07-09 Thread William Stein
On Wed, Jul 9, 2008 at 8:11 PM, David Philp <[EMAIL PROTECTED]> wrote: > > > This is a 'for the record' email describing how to use boost.python > with sage on Mac OS X. Thanks to the gentlefolk who walked me through > it (especially Carl Witty). > > I am assuming a working boost.python extension