On Thu, May 23, 2013 at 11:41 PM, Chris Barker - NOAA Federal <
chris.bar...@noaa.gov> wrote:
> On Thu, May 23, 2013 at 2:29 PM, Matthias Baas
> wrote:
>
> > From a user's point of view, I find that Windows installers as generated
> > by bdist_wininst still pr
On 22.05.13 18:30, Chris Barker - NOAA Federal wrote:
> Users also fall into two categories:
>
> 1) Folks that do Python development on OS-X much like Linux, etc --
> these folks are likely to use macports or homebrew, or are used to the
> .configure, make, make install dance. We don't need to do
Hi,
a while back there has been a discussion about Python 3 support in
bdist_mpkg. Basically, I was in the same situation as the original
poster and was looking for a way to produce binary packages for Python 3.
As it seemed that bdist_mpkg is not maintained anymore and it's using an
obsolete pack
On 25.01.11 22:24, Christopher Barker wrote:
>> You can find out the ABI version a particular version of gcc uses by
>> running the following command:
>>
>> g++ -E -dM -
> Any idea how to see what ABI version a given binary was compiled against?
Hm, I don't know. The above only prints a preproces
On 25.01.11 17:06, Christopher Barker wrote:
> On 1/25/11 1:20 AM, Brendan Simon (eTRIX) wrote:
>> Fatal Error: Mismatch between the program and library build versions
>> detected.
>> The library used 2.8 (no debug,Unicode,compiler with C++ ABI 1002,wx
>> containers,compatible with
Christopher Barker wrote:
> Greg Ewing wrote:
>> I've been thinking for a while about creating something
>> simpler that doesn't attempt any automatic module discovery
>> at all. You would be required to construct a project file
>> that explicitly lists all the required modules and libraries,
>> in
Christopher Barker wrote:
> import PIL._imagingft
>> Traceback (most recent call last):
>> File "", line 1, in
>> ImportError: dlopen(PIL/_imagingft.so, 2): Symbol not found:
>> _FSOpenResFile
>> Referenced from: PIL/_imagingft.so
>> Expected in: dynamic lookup
>>
>> This error does not
Christopher Barker wrote:
>> *** PIL CORE support not installed
>
> That sure doesn't look good!
>
>> *** TKINTER support not installed
>> --- JPEG support ok
>> --- ZLIB (PNG/ZIP) support ok
>> *** FREETYPE2 support not installed
>> *** LITTLECMS support not installed
>
> neither do those.
Ha!
Christopher Barker wrote:
> great -- are any of them running 10.4?
>
> I have little time, but here is the short version:
>
> The goal is to get a PIL binary that is statically linked to all of its
> dependencies, and those dependencies are all universal (32 bit PPC and
> Intel) and linked agains
Rodney Somerstein wrote:
> At 11:17 AM -0700 5/25/10, Christopher Barker wrote:
>> Honestly, I don't know if the Mac is in any poorer position with
>> regard to Python 3 as any other platform.
>>
>> NONE of the major packages I use have been ported to Py3 on any
>> platform: numpy, SciPy, wxPython.
aditya bhargava wrote:
> How do you determine which version of Python to build for? I'm on 10.4
> and I've got two versions of Python – python2.3 in /usr/bin/python and
> python2.5 in /opt/local/bin/python. python2.5 is my default (i.e. the
> one that shows when I run 'which python'), but the packa
Christopher Barker wrote:
> Much to my surprise, I had a little time to build some PIL binaries:
>
> http://dl.dropbox.com/u/855965/PIL-OSX-Binaries/PIL-1.1.7-py2.5-macosx10.5.mpkg.zip
> http://dl.dropbox.com/u/855965/PIL-OSX-Binaries/PIL-1.1.7-py2.6-macosx10.5.mpkg.zip
>
> I'd really like folks
Joe Strout wrote:
I've just stumbled across the Python-Ogre project
(http://www.pythonogre.com/). It looks fantastic, but the only binary
is for Windows. That seems a little silly for a set of
cross-platform-language bindings to a cross-platform library. :)
There are older build instructio
[EMAIL PROTECTED] wrote:
> Feat> I've carefully read the section about building extensions, ...
> Feat> but this doesn't tell me how to locate the right Python header
> Feat> file...
>
> Distutils takes care of that for you. All you should need to do is
>
> #include "Python.h"
>
Hi,
I have a question about distributing binary package on OSX (I'm still
rather new to OSX but now that I have a Mac I'd like to provide an OSX
binary of an Open Source package of mine).
I was using the bdist_mpkg distutils extension to create a binary and
could turn that into a *.dmg. Testing
15 matches
Mail list logo
