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 provide the nicest user experience with
On Wed, May 22, 2013 at 11:53 PM, Ronald Oussoren
wrote:
>> I'm using the
>> system zlib -- is that a bad idea? Should I build it too, to make sure
>> it matches the rest of it?
>>
>> (I do want the binaries to run anywhere the binary Python I'm using runs)
>
> It depends on the library.
OK -- it
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 provide the nicest user experience with OSX
> packages being a close second.
second? Aren't they essentially the same experience? But anyway..
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
On Thu, May 23, 2013 at 12:45 AM, Samuel John wrote:
> I am from the homebrew team and passionate python lover. I can almost feel
> your pain :-)
Thanks for joining the discussion -- really great to have a
homebrew-familiar person to discuss with.
However, and please to correct me if I'm wrong,
Hi,
I am from the homebrew team and passionate python lover. I can almost feel
your pain :-)
Some things install nice with pip, but others don't. That is why I started
to maintain a separate "tap" for additional homebrew python formulae like
pillow, numpy, scipy, matplotlib, pygame ... (one can
On 23 May, 2013, at 0:46, Chris Barker - NOAA Federal
wrote:
> Thanks Ronald,
>
> On Wed, May 22, 2013 at 2:53 PM, Ronald Oussoren
> wrote:
>
>> To move back onto topic, not relying on unix-level libraries in OSX is in a
>> good thing as it makes it easier to support multiple OSX versions
On 23 May, 2013, at 7:38, Chris Barker - NOAA Federal
wrote:
> I just poked a bit into the Anaconda Python distribution. their
> packages are simple tarballs, but I think they have a dependency
> management system of some sort.
>
> They deliver the dependencies as separate packages (tarballs),
I just poked a bit into the Anaconda Python distribution. their
packages are simple tarballs, but I think they have a dependency
management system of some sort.
They deliver the dependencies as separate packages (tarballs), one for
each lib. It looksl ike it all gets unpacked inot a sinlgle dir (i
Thanks Ronald,
On Wed, May 22, 2013 at 2:53 PM, Ronald Oussoren wrote:
> To move back onto topic, not relying on unix-level libraries in OSX is in a
> good thing as it makes it easier to support multiple OSX versions with a
> single set of binaries.
hmm -- I figured if it was a system lib, it
On 22 May, 2013, at 19:30, Chris Barker - NOAA Federal
wrote:
> Hey folks,
>
> I'm looking for advice, and maybe even some consensus among the
> MacPython community, on how to build and distribute packages with
> non-python dependencies.
>
> As we all know, a number of Python packages require
Hey folks,
I'm looking for advice, and maybe even some consensus among the
MacPython community, on how to build and distribute packages with
non-python dependencies.
As we all know, a number of Python packages require libs that are used
outside of python itself. These libs fall into (sort of) wha
12 matches
Mail list logo
