Re: [MacPorts] #14342: python25 drops modules by default, but python2[4] doesn't (js)
Hi js and Rainer, I've been following the MacPorts threads about Python for a few months now, trying to understand the problems and issues. My vote would be for Option 3: Add dropped mods to python24 and python25 as dependencies. My main goal is to write portable scientific Python applications that will work on both Mac and Windows On Fri, 14 Mar 2008 01:52:02 +0900, js <ebgssth@gmail.com> wrote: I think it's about a time to decide how we handle this. I wanted to change python24 to be python25-like design for consistency. Derek disagreed this idea from python24 users standpoint. Rainer seemed to agree with me, but might not like adding dropped mods to python port as dependencies. Options: 1. Change python24 to drop standard mods just as python25 does. 2. Don't change anything. 3. 1+add dropped mods to python24 and python25 as dependencies I like the first one. How about you? On Wed, Mar 12, 2008 at 10:08 PM, js <ebgssth@gmail.com> wrote:
The benefit is that python24 and python25 both uses almost same standard mods. Please note that I'm not sure adding this dependency is good thing. I just wanted to say keeping python ports similar would preferable, in my opinion.
On Wed, Mar 12, 2008 at 6:12 AM, Rainer Müller <raimue@macports.org> wrote:
js wrote:
If I add zlib dependency to python24, I'd also add it to python25.
But if you you add it as dependency, what is the benefit from putting it in its own port?
Rainer
Hi js and Rainer, [I accidentally hit send, before I finished my last message. Here is what I wanted to write.] I've been following the MacPorts threads about Python for a few months now, trying to understand the problems and issues. My vote would be for Option 3: Add dropped mods to python24 and python25 as dependencies. My main Python goal is to write portable scientific Python applications that will work on both Mac and Windows. To that end, Python on Mac should be as close to the standard distribution of Python as possible. Dropping modules from the standard distribution breaks things. I spent most of a week tracking down problems why my simple, portable application did not work on MacPorts' Python, only to finally discover that I had to add additional ports to get what was one install on Windows or Unix or Linux. (py-hashlib was missing.) Why? I thought the main goal of MacPorts was to make installation simple. Splitting standard distributions into multiple ports is going in the opposite direction. If someone wants a minimal install, that could be a variant, but the default should be a full install. Thanks for working on this. -- Harry Parker On Fri, 14 Mar 2008 01:52:02 +0900, js <ebgssth@gmail.com> wrote:
I think it's about a time to decide how we handle this. I wanted to change python24 to be python25-like design for consistency. Derek disagreed this idea from python24 users standpoint. Rainer seemed to agree with me, but might not like adding dropped mods to python port as dependencies.
Options: 1. Change python24 to drop standard mods just as python25 does. 2. Don't change anything. 3. 1+add dropped mods to python24 and python25 as dependencies
I like the first one. How about you?
On Wed, Mar 12, 2008 at 10:08 PM, js <ebgssth@gmail.com> wrote:
The benefit is that python24 and python25 both uses almost same standard mods. Please note that I'm not sure adding this dependency is good thing. I just wanted to say keeping python ports similar would preferable, in my opinion.
On Wed, Mar 12, 2008 at 6:12 AM, Rainer Müller <raimue@macports.org> wrote:
js wrote:
If I add zlib dependency to python24, I'd also add it to python25.
But if you you add it as dependency, what is the benefit from putting it in its own port?
Rainer
participants (1)
-
Harry Parker