On Thu, May 28, 2009 at 10:01 AM, John Hunter wrote:
> On Thu, May 28, 2009 at 9:57 AM, Charlie Moad wrote:
>
>> I'll have to check my home computer tonight. I never saw your note
>> about libpng either. Again, I'll poke a little more tonight once I
>> get home to my machine and update you.
>
>
On Thu, May 28, 2009 at 9:57 AM, Charlie Moad wrote:
> I'll have to check my home computer tonight. I never saw your note
> about libpng either. Again, I'll poke a little more tonight once I
> get home to my machine and update you.
The debugger indicates the dreaded mscvrt is still in the bina
On Thu, May 28, 2009 at 10:52 AM, John Hunter wrote:
> On Thu, May 28, 2009 at 9:37 AM, Charlie Moad wrote:
>
>> I think setuptools should be a requirement in the same way numpy is.
>>
>> The latest "ez_setup.py" script has 2.6 included.
>> http://peak.telecommunity.com/dist/ez_setup.py
>>
>> You
On Thu, May 28, 2009 at 9:37 AM, Charlie Moad wrote:
> I think setuptools should be a requirement in the same way numpy is.
>
> The latest "ez_setup.py" script has 2.6 included.
> http://peak.telecommunity.com/dist/ez_setup.py
>
> You should be able to do the normal, "python ez_setup.py"
OK, I g
On Thu, May 28, 2009 at 10:34 AM, John Hunter wrote:
> On Thu, May 28, 2009 at 9:25 AM, John Hunter wrote:
>> On Thu, May 28, 2009 at 9:06 AM, John Hunter wrote:
>>> On Thu, May 28, 2009 at 8:57 AM, Charlie Moad wrote:
Another note. I ran into problems when trying to create the build in
>
On Thu, May 28, 2009 at 9:25 AM, John Hunter wrote:
> On Thu, May 28, 2009 at 9:06 AM, John Hunter wrote:
>> On Thu, May 28, 2009 at 8:57 AM, Charlie Moad wrote:
>>> Another note. I ran into problems when trying to create the build in
>>> a directory that had spaces. (e.g. C:\Documents and Set
On Thu, May 28, 2009 at 10:25 AM, John Hunter wrote:
> On Thu, May 28, 2009 at 9:06 AM, John Hunter wrote:
>> On Thu, May 28, 2009 at 8:57 AM, Charlie Moad wrote:
>>> Another note. I ran into problems when trying to create the build in
>>> a directory that had spaces. (e.g. C:\Documents and Se
On Thu, May 28, 2009 at 9:06 AM, John Hunter wrote:
> On Thu, May 28, 2009 at 8:57 AM, Charlie Moad wrote:
>> Another note. I ran into problems when trying to create the build in
>> a directory that had spaces. (e.g. C:\Documents and Settings\).
>> Try running everything in a top level dir.
On Wed, May 27, 2009 at 11:08 PM, Charlie Moad wrote:
> I've spent the last couple of days writing the win32 equivalent
> of John's osx release scripts for MinGW. It patches distutils at
> runtime to exclude the msvcr link, hence we should no longer need to
> modify distutils. I have tested
It's strange that I didn't run into spacing issues.
sdist --formats=gztar
- Charlie
On Thu, May 28, 2009 at 9:47 AM, John Hunter wrote:
> On Wed, May 27, 2009 at 11:08 PM, Charlie Moad wrote:
>> I've spent the last couple of days writing the win32 equivalent
>> of John's osx release script
On Thu, May 28, 2009 at 8:57 AM, Charlie Moad wrote:
> Another note. I ran into problems when trying to create the build in
> a directory that had spaces. (e.g. C:\Documents and Settings\).
> Try running everything in a top level dir.
That's not it -- I avoid spaces like the plague.
I am n
On Thu, May 28, 2009 at 8:56 AM, Charlie Moad wrote:
> It's strange that I didn't run into spacing issues.
>
> sdist --formats=gztar
Did you maybe add the comments after you had built the dependencies,
so that branch wasn't executed when you compiled?
Thanks for the sdist flag -- I'll update the
Another note. I ran into problems when trying to create the build in
a directory that had spaces. (e.g. C:\Documents and Settings\).
Try running everything in a top level dir.
- Charlie
On Thu, May 28, 2009 at 9:56 AM, Charlie Moad wrote:
> It's strange that I didn't run into spacing issue
13 matches
Mail list logo
