Re: [Pythonmac-SIG] Marking the pre-built extensions as Intel-capable...

On 28-mrt-2006, at 18:20, Christopher Barker wrote: > Ronald Oussoren wrote: > >> Before anyone starts coding, what should happen when you double-click >> on an egg? I'd say this should bring up a dialog that allows you to >> install the egg and possibly set some options. Installation will >> b

Re: [Pythonmac-SIG] Marking the pre-built extensions as Intel-capable...

> Couldn't we put a *.egg into a *.mpkg? and get the best of both worlds? That would be my vote. Bill ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig

Re: [Pythonmac-SIG] Marking the pre-built extensions as Intel-capable...

On 28-mrt-2006, at 18:26, Christopher Barker wrote: > Ronald Oussoren wrote: > >> For casual users it is easier to install mpkgs, hence we'll need >> mpkgs until someone writes the tool that allows one to double-click >> on eggs to install them. I'm tempted to do so myself just to avoid >> packag

Re: [Pythonmac-SIG] Marking the pre-built extensions as Intel-capable...

Ronald Oussoren wrote: > For casual users it is easier to install mpkgs, hence we'll need > mpkgs until someone writes the tool that allows one to double-click > on eggs to install them. I'm tempted to do so myself just to avoid > packaging stuff twice :-) > > Mpkgs have another advantage: they a

Re: [Pythonmac-SIG] Marking the pre-built extensions as Intel-capable...

Ronald Oussoren wrote: > Before anyone starts coding, what should happen when you double-click > on an egg? I'd say this should bring up a dialog that allows you to > install the egg and possibly set some options. Installation will be done > using easy_install. That sounds good to me. Does easy-

Re: [Pythonmac-SIG] Marking the pre-built extensions as Intel-capable...

On 28-mrt-2006, at 1:18, Bob Ippolito wrote: > > On Mar 27, 2006, at 2:55 PM, Christopher Barker wrote: > >> Bob Ippolito wrote: >> >>> That whole section really needs to be restructured to address the >>> common questions and issues people have regarding finding the right >>> packages for them.

Re: [Pythonmac-SIG] Marking the pre-built extensions as Intel-capable...

On 28-mrt-2006, at 3:01, Nicholas Riley wrote: > On Mon, Mar 27, 2006 at 04:00:07PM -0800, Christopher Barker wrote: >> What happens if you double-click on a *.egg? > > That'd be an incredibly cool utility to have, and a lot easier to > write than something like PackageManager. Before anyone sta

Re: [Pythonmac-SIG] Marking the pre-built extensions as Intel-capable...

> Without any experience with "eggs" (I believe that they are another > Phillip Eby brainstorm?), can I suggest that a standard command-line Yep, they are. > Is there a specification for the "egg" format? http://peak.telecommunity.com/DevCenter/PythonEggs They're zipfiles containing additional

Re: [Pythonmac-SIG] Marking the pre-built extensions as Intel-capable...

On Mar 27, 2006, at 5:13 PM, Bill Janssen wrote: >>> I'd certainly prefer eggs where possible, but transitionally we're >>> definitely going to need *.mpkgs. Maybe both for now, and/or >>> separate >>> pages for .mpkgs and binary eggs? >> >> What happens if you double-click on a *.egg? >> >> I

Re: [Pythonmac-SIG] Marking the pre-built extensions as Intel-capable...

On Mar 27, 2006, at 4:00 PM, Christopher Barker wrote: > Bob Ippolito wrote: > >> No, I mean that that URL won't directly list any packages. It'll >> be a >> listing of package lists and enough information to direct a newish >> user >> to the right list. > > Then yes, that's a great idea. I

Re: [Pythonmac-SIG] Marking the pre-built extensions as Intel-capable...

On Mar 27, 2006, at 4:57 PM, Christopher Barker wrote: > Christopher Barker wrote: > >> Then yes, that's a great idea. I am, as we e-speak, reworking >> those pages with a different structure now. I'm no web designer, >> but it should give us something that someone can make prettier if >> t

Re: [Pythonmac-SIG] Marking the pre-built extensions as Intel-capable...

> > I'd certainly prefer eggs where possible, but transitionally we're > > definitely going to need *.mpkgs. Maybe both for now, and/or separate > > pages for .mpkgs and binary eggs? > > What happens if you double-click on a *.egg? > > I like that anyone with OS-X can figure out how to install

Re: [Pythonmac-SIG] Marking the pre-built extensions as Intel-capable...

> > Could someone please put a note on http://pythonmac.org/packages/ to > > say that the packages listed there are all PPC-only? > > Done Looks good, thanks. Bill ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/l

Re: [Pythonmac-SIG] Marking the pre-built extensions as Intel-capable...

On Mon, Mar 27, 2006 at 04:00:07PM -0800, Christopher Barker wrote: > What happens if you double-click on a *.egg? That'd be an incredibly cool utility to have, and a lot easier to write than something like PackageManager. -- Nicholas Riley <[EMAIL PROTECTED]> |

Re: [Pythonmac-SIG] Marking the pre-built extensions as Intel-capable...

Bob Ippolito wrote: > No, I mean that that URL won't directly list any packages. It'll be a > listing of package lists and enough information to direct a newish user > to the right list. Then yes, that's a great idea. I am, as we e-speak, reworking those pages with a different structure now.

Re: [Pythonmac-SIG] Marking the pre-built extensions as Intel-capable...

On Mar 27, 2006, at 2:55 PM, Christopher Barker wrote: > Bob Ippolito wrote: > >> That whole section really needs to be restructured to address the >> common questions and issues people have regarding finding the right >> packages for them. > > great idea. > >> I think I'd like to turn http://pyt

Re: [Pythonmac-SIG] Marking the pre-built extensions as Intel-capable...

Bob Ippolito wrote: > That whole section really needs to be restructured to address the > common questions and issues people have regarding finding the right > packages for them. great idea. > I think I'd like to turn http://pythonmac.org/ > packages/ into just a launch pad for finding a li

Re: [Pythonmac-SIG] Marking the pre-built extensions as Intel-capable...

On Mar 27, 2006, at 11:36 AM, Bill Janssen wrote: > I'm looking over the downloads page again, thinking about what we need > to do to support the Universal builds. > > First off, the discussion last week about which packages will work > with it seems very important. > > Who's got edit access to p

[Pythonmac-SIG] Marking the pre-built extensions as Intel-capable...

I'm looking over the downloads page again, thinking about what we need to do to support the Universal builds. First off, the discussion last week about which packages will work with it seems very important. Who's got edit access to pythonmac.org? Could someone please put a note on http://pythonm