This not be the right list for this but maybe someone can point me in
the right direction. Apologies in advance.
In my day job, I work in an environment with many (>10) Mac OS X &
Linux boxes and python is getting a fair amount of usage.
Unfortunately, a number of us have custom installations
Bill Janssen wrote:
>1) We should no longer point people to Jack's site, we point them to
> the python.org Mac download page instead.
Agree. Having links to the old MacPython site in places where folk expect to
find up-to-date information doesn't help.
Also, if there's somewhere to provide a
Many thanks to you Bob.
You're a community treasure.
> Also note that the Image module probably isn't broken (don't have
> PIL installed at the moment, can't check). Constants don't
> automagically just insert themselves into your script. You should
> be able to reference it with Image.BI
Bill Janssen wrote:
> In my opinion, the problem is the term "MacPython". Python is Python,
> period, and we should just call it that, even if it's running on the Mac
> platform. Perhaps this was different in the pre-OSX days, but not now.
On OS X I think of the 'MacPython' name more as a way t
Thank you Bob.
>> Very simple beginner script. Not sure why it doesn't write files
>> after py2appletizing.
>> Seems to work just fine from the command line. What am I missing?
>
> You're missing the fact that the current directory in a py2app-
> generated applet is inside the Resources folder
On Apr 19, 2006, at 10:23 AM, corporate user wrote:Naively, I start with a script in my ~/src folder and I end with an application in my ~/src folder. Like a typical Apple user, I treat the bundle as the code itself and don't bother to dwell on its content or structure. I now understand what
On 19/04/2006, at 03:23, Bill Janssen wrote:
> 3) What about the following:
>
> 2. MacPython Modules
> 2.1 macpath -- MacOS path manipulation functions
> 2.2 macfs -- Various file system services
> 2.2.1 FSSpec Objects
> 2.2.2 Alias Objects
> 2.2.3 F
On Apr 19, 2006, at 6:38, corporate user wrote:
> Many thanks to you Bob.
> You're a community treasure.
>
>
>> Also note that the Image module probably isn't broken (don't have
>> PIL installed at the moment, can't check). Constants don't
>> automagically just insert themselves into your script
I think one frequent reason people fall back on 'from xxx import *' is simply that typing the whole module name over and over gets tedious and makes the code sprawl. I find 'import xxx as yyy' very useful for this, since it can give you a nice short alias, still readable if you're careful about nam
> >4.2 Carbon.AH -- Apple Help
>
> Do nothing.
Much like Apple Help itself :-).
Bill
___
Pythonmac-SIG maillist - [email protected]
http://mail.python.org/mailman/listinfo/pythonmac-sig
On Wed, Apr 19, 2006 at 02:38:22PM +0100, has wrote:
> >2.3 ic -- Access to Internet Config
>
> No idea about this. Anyone else know if this is still working/relevant?
It is basically deprecated for LaunchServices now. It would be really
good if we could get a decent LaunchServices bindi
Thanks, Has.
I was hoping someone would go through that list bit-by-bit.
I'm still in favor of simply removing outdated and dangerous docs, but
perhaps there's some effective way of thoroughly marking them as bad,
instead.
Bill
___
Pythonmac-SIG mailli
Jacob Rus wrote:
> Argh, never mind that message. I see now that psyco is clearly labeled
> as only working on i386. Nothing to see here, move along.
It'd be nice to know how/if it works on an Intel Mac, however. Anyone?
-Chris
--
Christopher Barker, Ph.D.
Oceanographer
Bob Ippolito wrote:
> *ALWAYS* prefer convenience over space. Never make separate
> distributions for i386 and PPC. Simplicity is key.
Absolutely.
> I will no longer accept single-architecture packages for
> pythonmac.org/packages except under special circumstances
However... Right now, we d
corporate user wrote:
> I'm forming the opinion that
> "from XXX import *" should be banned from all introduction, tutorial
> and example materials.
Actually, it should be banned from virtually ALL user code! But tutorial
and examples are a start!
-Chris
--
Christopher Barker, Ph.D.
Ocea
corporate user wrote:
> I made the assumption that since py2app automagically created an
> Apple application without my having to know anything about a bundle
> or its structure, that it would also create path emulation as well.
I'm not sure that's your problem. I think your problem is really
On Apr 19, 2006, at 12:53 PM, Christopher Barker wrote:
> corporate user wrote:
>> I'm forming the opinion that
>> "from XXX import *" should be banned from all introduction, tutorial
>> and example materials.
>
> Actually, it should be banned from virtually ALL user code! But
> tutorial
> and e
On Apr 19, 2006, at 9:49, Christopher Barker wrote:
> My suggestion:
>
> A ExtraLibs.mpkg, right there with the packages on pythonmac.org that
> includes Universal shared libs required by some common packages. They
> could perhaps be installed in the Python Framework, so they won't
> interfere wit
On Apr 19, 2006, at 9:14, Bill Janssen wrote:
> I'm still in favor of simply removing outdated and dangerous docs, but
> perhaps there's some effective way of thoroughly marking them as bad,
> instead.
Put in doc sections entitled Deprecated and Obsolete and do the same
for the web and wiki.
I
Bill Janssen wrote:
>Thanks, Has.
>
>I was hoping someone would go through that list bit-by-bit.
See also NR's post and my reply to it; anything Internet Config-related looks
reasonable to add to the 'deprecate' list. Hopefully there'll be a few more
yeas/nays on it from other folks; like I say
> There's the flat logo, but the logo I was pointing to was a version
> that's shaded a bit to look slightly raised and rounded.
Were you looking for something more like [this][1]?
-Jacob
[1]: http://hcs.harvard.edu/~jrus/python/Glassy-Icon.png
___
Py
Nicholas Riley wrote:
> > >2.3 ic -- Access to Internet Config
> >
> > No idea about this. Anyone else know if this is still working/relevant?
>
>It is basically deprecated for LaunchServices now.
Righto, add it to the 'deprecate' list then.
> It would be really good if we could get a d
On Apr 19, 2006, at 10:03, Zachery Bir wrote:
> On Apr 19, 2006, at 12:53 PM, Christopher Barker wrote:
>
>> corporate user wrote:
>>> I'm forming the opinion that
>>> "from XXX import *" should be banned from all introduction, tutorial
>>> and example materials.
>>
>> Actually, it should be bann
Bob Ippolito wrote:
>>In addition, all mentions of OS 9 should either be expunged (e.g. the 'using
>>Python on Mac OS 9' chapter) or changed to 'not supported' (should they still
>>need to be documented for any reason).
>
>Mac OS 9 is definitely no longer supported at all. The *final* release f
On Apr 19, 2006, at 10:33, Jacob Rus wrote:
>> There's the flat logo, but the logo I was pointing to was a version
>> that's shaded a bit to look slightly raised and rounded.
>
> Were you looking for something more like [this][1]?
>
> -Jacob
>
> [1]: http://hcs.harvard.edu/~jrus/python/Glassy-Ico
Bob Ippolito:
> It does just copy Resources. You'll have to use the latest py2app 0.2
> maintenance branch from svn.
>
> http://svn.red-bean.com/bob/py2app/branches/py2app-0.2-maint/
Thanks Bob,
I checked out py2app from the URL given, ran setup.py as instructed.
When I run python setup.py p
On 18-apr-2006, at 23:48, Christopher Barker wrote:
> Ronald Oussoren wrote:
>> On 13-apr-2006, at 18:47, Zachary Pincus wrote:
>>> Also, a related query: Is there somewhere in the Python Framework
>>> structure that is appropriate for placing dynamic libraries that
>>> Python would link to?
>
>>
Jacob Rus wrote:
> > There's the flat logo, but the logo I was pointing to was a version
> > that's shaded a bit to look slightly raised and rounded.
>
>Were you looking for something more like [this][1]?
>[1]: http://hcs.harvard.edu/~jrus/python/Glassy-Icon.png
The snake logo you've used there i
On 18-apr-2006, at 22:59, Advertising Department wrote:
> (I'm totally confused about the nine versions of python for Mac OS X,
> the defunct or just not updated for 2 years MacPython pages, the
> current state of the macintosh specific library modules, etc.)
>
> To give my 2 cents...
> It doesn'
On 19-apr-2006, at 0:11, Jacob Rus wrote:
> I wrote:
>> I couldn't compile [psyco][1] using the 2.4.3 universal version of
>> Python on my 12" powerbook. I'm wondering if this is just a problem
>> with universal Python, or if psycho doesn't compile in general
>> under OS X.
>
> Argh, never min
>> [1]: http://hcs.harvard.edu/~jrus/python/Glassy-Icon.png
>
> Much better. In fact a great deal better--its looks worthy of the Mac.
> I could even say this is great. But, pushing the envelope a bit if
> you don't think I am being too demanding...
> Can you 'aqua-fy it' little-- give it that s
On 19-apr-2006, at 2:23, Bill Janssen wrote:
> Just looking at the docs, I'm trying to figure out what's good and
> what's bad.
>
> 1) We should no longer point people to Jack's site, we point them to
>the python.org Mac download page instead.
Right.
>
> 2) references to PythonIDE and Packa
Bob Ippolito wrote:
[EasyDialogs]
>>Didn't see a waste dependency in the module; you sure about that? I've tried
>>it and it still seems to be working okay (as well as it ever did, anyway), in
>>which case immediate removal is not necessary. I wouldn't be averse to
>>deprecating it just on gene
On Apr 19, 2006, at 12:08, Jacob Rus wrote:
>>> [1]: http://hcs.harvard.edu/~jrus/python/Glassy-Icon.png
>>
>> Much better. In fact a great deal better--its looks worthy of the
>> Mac.
>> I could even say this is great. But, pushing the envelope a bit if
>> you don't think I am being too demand
Bob Ippolito:
>>
>> Apparently, py2app is expecting a i386 python version? Why? How can I
>> tell it to expect and use the PPC version?
>
> I actually don't know, I didn't write those patches. I won't have time
> to look into this for at least a week, but you might want to dig into
> the source
On 19-apr-2006, at 15:38, has wrote:
>
>
>>2.1 macpath -- MacOS path manipulation functions
>
> Deprecate. Also note that the 2.4.3 documentation now says "It can
> be used to manipulate old-style Macintosh pathnames on Mac OS X (or
> any other platform)." which is incorrect (it uses
On 19-apr-2006, at 18:14, Bill Janssen wrote:
> Thanks, Has.
>
> I was hoping someone would go through that list bit-by-bit.
>
> I'm still in favor of simply removing outdated and dangerous docs, but
> perhaps there's some effective way of thoroughly marking them as bad,
> instead.
I'm in favour
On 19-apr-2006, at 18:49, Christopher Barker wrote:
> Bob Ippolito wrote:
>> *ALWAYS* prefer convenience over space. Never make separate
>> distributions for i386 and PPC. Simplicity is key.
>
> Absolutely.
>
>> I will no longer accept single-architecture packages for
>> pythonmac.org/packages
> It is annoying that www.python.org/download/mac doesn't mention the
> universal installer. Could someone please fix that?
Will do. Should this replace the dual-installer procedure that's
mentioned there? For both 10.3 and 10.4?
Bill
___
Pythonmac-SI
On 19-apr-2006, at 19:33, Jacob Rus wrote:
>> There's the flat logo, but the logo I was pointing to was a version
>> that's shaded a bit to look slightly raised and rounded.
>
> Were you looking for something more like [this][1]?
That one looks nice.
Ronald
>
> -Jacob
>
> [1]: http://hcs.harva
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ronald Oussoren wrote:
>>
>>>4.2 Carbon.AH -- Apple Help
>> Do nothing.
>
> Documentation would be nice :-)
>
>>
I might be able to help here. I've actually used this module in
non-Python apps (I used to use in Tcl/Tk apps by exec'ing 'pyth
On Apr 19, 2006, at 12:52, Ronald Oussoren wrote: 2.1 macpath -- MacOS path manipulation functions Deprecate. Also note that the 2.4.3 documentation now says "It can be used to manipulate old-style Macintosh pathnames on Mac OS X (or any other platform)." which is incorrect (it uses POSI
Bill> But the NEWS section of python.org is totally disfunctional.
Bill> Months go by without anyone bothering to add anything to it; I
Bill> think the trouble is that no one knows what the "add" procedure
Bill> is.
I tend to agree with you. Given all the recent changes to the sit
>
> On 19-apr-2006, at 18:14, Bill Janssen wrote:
>
> > Thanks, Has.
> >
> > I was hoping someone would go through that list bit-by-bit.
> >
> > I'm still in favor of simply removing outdated and dangerous docs, but
> > perhaps there's some effective way of thoroughly marking them as bad,
> > ins
Ronald> It is annoying that www.python.org/download/mac doesn't mention
Ronald> the universal installer.
It does now. It will take a few minutes for the global build process to
update the website, but I checked in a minimal change to Subversion.
Skip
Ronald wrote:
>Macpath deals with OS9/Carbon style paths (Volume:directory:file instead of
>/Volume/directory/file).
Don't know where you're seeing this; I've tried a few of the functions and none
work with HFS-style paths, only POSIX-style paths. The documentation describes
it as an OS9 impl
On 19-apr-2006, at 22:06, Bill Janssen wrote:
>> It is annoying that www.python.org/download/mac doesn't mention the
>> universal installer. Could someone please fix that?
>
> Will do. Should this replace the dual-installer procedure that's
> mentioned there? For both 10.3 and 10.4?
The univer
On 19-apr-2006, at 22:11, Kevin Walzer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Ronald Oussoren wrote:
>
>>>
4.2 Carbon.AH -- Apple Help
>>> Do nothing.
>>
>> Documentation would be nice :-)
>>
>>>
>
> I might be able to help here. I've actually used this module in
On Apr 19, 2006, at 13:04, Ronald Oussoren wrote:I'll post the script I'm using to build universal packages this weekend. I have recipes for the software I'm using and several other. That includes PIL (including jpeg, tif and freetype support).I'll put mine on my iDisk and send you a link. I'd li
On 19-apr-2006, at 22:13, Bill Janssen wrote:
>>
>> On 19-apr-2006, at 18:14, Bill Janssen wrote:
>>
>>> Thanks, Has.
>>>
>>> I was hoping someone would go through that list bit-by-bit.
>>>
>>> I'm still in favor of simply removing outdated and dangerous
>>> docs, but
>>> perhaps there's some e
On 19-apr-2006, at 22:20, [EMAIL PROTECTED] wrote:
>
> Ronald> It is annoying that www.python.org/download/mac doesn't
> mention
> Ronald> the universal installer.
>
> It does now. It will take a few minutes for the global build
> process to
> update the website, but I checked in a m
NEWS was broken long before the new site.
Bill
___
Pythonmac-SIG maillist - [email protected]
http://mail.python.org/mailman/listinfo/pythonmac-sig
Ronald> I don't know who will do it, I do know that we won't get very
Ronald> far by just talking about it ;-). Pick some part that you
Ronald> consider broken and propose how this can be fixed. I do want to
Ronald> fix as many bugs as possible for python 2.5, but that won't
Ro
On 19-apr-2006, at 22:27, Daniel Lord wrote:
>
> On Apr 19, 2006, at 13:04, Ronald Oussoren wrote:
>
>> I'll post the script I'm using to build universal packages this
>> weekend.
>> I have recipes for the software I'm using and several other. That
>> includes
>> PIL (including jpeg, tif and fr
has wrote:
> Jacob Rus wrote:
>>> There's the flat logo, but the logo I was pointing to was a version
>>> that's shaded a bit to look slightly raised and rounded.
>> Were you looking for something more like [this][1]?
>> [1]: http://hcs.harvard.edu/~jrus/python/Glassy-Icon.png
>
> The snake logo y
On 19-apr-2006, at 22:23, has wrote:
> Ronald wrote:
>
>> Macpath deals with OS9/Carbon style paths (Volume:directory:file
>> instead of /Volume/directory/file).
>
> Don't know where you're seeing this; I've tried a few of the
> functions and none work with HFS-style paths, only POSIX-style
On Apr 19, 2006, at 13:41, Jacob Rus wrote:Ok, got it. Well, I've now put more time into this than I wanted to, but I've got a glassy version of the correct python logo at full size, [here][4]. Let me know what you all think. If it looks good to everyone, I can make a .py icon like the one li
I tested my Universal PIL installer for Python 2.4 on 10.4 on my
MacbookPro but not PPC (my daughters refuse to quit Zoo Tycoon 2 and
log off so I can tinker with it ;-) and it seems to work though I
don't have a rigorous PIL test suite. The zip file is on my iDisk if
anyone wants to give i
On Wed, Apr 19, 2006 at 04:41:59PM -0400, Jacob Rus wrote:
> Ok, got it. Well, I've now put more time into this than I wanted to,
> but I've got a glassy version of the correct python logo at full size,
> [here][4]. Let me know what you all think. If it looks good to
> everyone, I can make a
First thing that hit my brain: "That's IT." wrote:On Wed, Apr 19, 2006 at 04:41:59PM -0400, Jacob Rus wrote:
> Ok, got it. Well, I've now put more time into this than I wanted to,> but I've
Ok, what do you all think of these script and compiled script icons:
PNG: http://hcs.harvard.edu/~jrus/python/python-icons-a1.png
ZIP: http://hcs.harvard.edu/~jrus/python/python-icons-a1.zip
The zip file contains icns files, png files, and also folders with the
icons applied.
I'm glad to provid
Bob Ippolito wrote:
> The libs should all be statically linked to the extensions, they
> shouldn't be separate in the installer.
Ronald Oussoren wrote:
> I'd prefer to have fully self contained packages, and preferably
> eggs at that. Having a shared libary makes it *harder* to independendly
> up
Jacob Rus wrote:
> Ok, what do you all think of these script and compiled script icons:
They look great, but what the heck is "DATA"?
-Chris
--
Christopher Barker, Ph.D.
Oceanographer
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Poi
On 4/19/06 1:41 PM, "Jacob Rus" <[EMAIL PROTECTED]> wrote:
> Ok, got it. Well, I've now put more time into this than I wanted to,
> but I've got a glassy version of the correct python logo at full size,
> [here][4]. Let me know what you all think. If it looks good to
> everyone, I can make a .p
Christopher Barker wrote:
> They look great, but what the heck is "DATA"?
It was has's [idea][1] for what a .pyo/.pyc icons should look like,
similar to how script editor allows saving of plain text .applescript
files with an icon labeled "TEXT".
[1]: http://mail.python.org/pipermail/pythonmac
Well, I was planning on fixing the documentation, but apparently the
process requires a level of bureaucracy I'm just not willing to go
through (though I can see why it might be necessary). I can't just
check out the TeX sources and fix them, then check them back in.
Instead, I apparently have to
On Apr 19, 2006, at 15:53, Christopher Barker wrote:
> Bob Ippolito wrote:
>> The libs should all be statically linked to the extensions, they
>> shouldn't be separate in the installer.
>
> Ronald Oussoren wrote:
>> I'd prefer to have fully self contained packages, and preferably
>> eggs at that.
On 4/19/06, Jacob Rus <[EMAIL PROTECTED]> wrote:
> Ok, what do you all think of these script and compiled script icons:
>
> PNG: http://hcs.harvard.edu/~jrus/python/python-icons-a1.png
> ZIP: http://hcs.harvard.edu/~jrus/python/python-icons-a1.zip
>
> The zip file contains icns files, png files, an
Jacob,
Looks fine.
It's interesting to look at the icons for TextEdit, in
/Applications/TextEdit.app/Contents/Resources/*.icns.
And looking at the XCode icons
(/Developer/Applications/Xcode.app/Contents/Resources/*.icns), it
looks like the "Mac way" of doing code icons (like for .py files) is
to
I decide to create a droplet from py2app in my copious spare time for
a few minutes earlier and I noticed some errors in the Console plus
the code is simply printing out all the strings in sys.argv plus, of
course given the error, the paths of the files dropped on it never
showed up in sys.
Bill Janssen wrote:
> It's interesting to look at the icons for TextEdit, in
> /Applications/TextEdit.app/Contents/Resources/*.icns.
>
> And looking at the XCode icons
> (/Developer/Applications/Xcode.app/Contents/Resources/*.icns), it
> looks like the "Mac way" of doing code icons (like for .py f
I found two articles on creating icons that may provide some info.
http://www.oreillynet.com/lpt/a/866 and http://www.oreillynet.com/lpt/a/964.
Bill
___
Pythonmac-SIG maillist - [email protected]
http://mail.python.org/mailman/listinfo/pythonma
> No, I disagree. If there is any text, it should be in dark gray 18
> point Lucida Grande, as per the HIG. XCode uses colored file extensions
> in its document graphics because it deals with many different types of
> source files, and this keeps them distinguishable.
It's not just XCode. *U
Bill Janssen wrote:
>> No, I disagree. If there is any text, it should be in dark gray 18
>> point Lucida Grande, as per the HIG. XCode uses colored file
>> extensions in its document graphics because it deals with many
>> different types of source files, and this keeps them
>> distinguishable.
Hi... I been happily running 2.4.1 on my mac but i decided to load the
universal installer on a different mac (that we plan to use for
performance) and use 2.4.3 ... i mean why install and old version right
... uhmm ... anyway 2.4.3 is causing me much acid indigestion and is
not playing nice
>> Jacob Rus wrote:
>>
There's the flat logo, but the logo I was pointing to was a version
that's shaded a bit to look slightly raised and rounded.
>>> Were you looking for something more like [this][1]?
>>> [1]: http://hcs.harvard.edu/~jrus/python/Glassy-Icon.png
>>>
>> The snake lo
On 19-Apr-06, at 8:57 PM, [EMAIL PROTECTED] wrote:Christopher Barker wrote: > They look great, but what the heck is "DATA"? It was has's [idea][1] for what a .pyo/.pyc icons should look like, similar to how script editor allows saving of plain text .applescript files with an icon labeled "TEXT".
On 20-Apr-06, at 12:15 AM, [EMAIL PROTECTED] wrote:From: Jacob Rus <[EMAIL PROTECTED]> Date: April 19, 2006 10:06:34 PM EDT (CA) To: [email protected] Subject: Re: [Pythonmac-SIG] Fwd: MacPython icon mockup Bill Janssen wrote: No, I disagree. If there is any text, it should be in dark gra
Daniel Lord wrote:
> That sound reasonable, but not what I did--I installed them in /usr/
> local/lib & include.
I've done that, but the only way I could make sure that they got
statically linked was to make sure that there were not dynamic versions
of the same libs anywhere else on the search
Jacob Rus wrote:
> Christopher Barker wrote:
> > They look great, but what the heck is "DATA"?
>
> It was has's [idea][1] for what a .pyo/.pyc icons should look like,
> similar to how script editor allows saving of plain text .applescript
> files with an icon labeled "TEXT".
Well, a script is
On Apr 19, 2006, at 21:41, Christopher Barker wrote:
> Well, a script is text, but a .pyc file is not Data. Maybe "bytecode",
> which is too long, or "bytes" or "code" or ".pyc" or ???
I think it should be an Apple with a bite out of it--get it? Apple,
snake, apple, byte .
I kill myself ;-) Ok
Christopher Barker wrote:
> Jacob Rus wrote:
>> Christopher Barker wrote:
>> > They look great, but what the heck is "DATA"?
>> It was has's [idea][1] for what a .pyo/.pyc icons should look like,
>> similar to how script editor allows saving of plain text .applescript
>> files with an icon label
thank you bob you rock!
\m/ (>.<) \m/
this totally works ... (for anyone else needing to dumb down to 2.4.1)
cheers all...
-kp--
On Apr 20, 2006, at 1:02 AM, Bob Ippolito wrote:
>
> On Apr 19, 2006, at 7:55 PM, kevin parks wrote:
>
>> How do i uninstall 2.4.3?
>> so that i can dial back to
Brendan Simons wrote:
> I like it, but Aqua has tuned down a lot its glassiness in recent
> years. I would tone down the difference between highlights and shadows
> myself, but I'm not going to argue about it :)
You're probably right, but make sure you look at the actual icon files
(in the zi
On Apr 19, 2006, at 22:47, Jacob Rus wrote:Brendan Simons wrote: I like it, but Aqua has tuned down a lot its glassiness in recent years. I would tone down the difference between highlights and shadows myself, but I'm not going to argue about it :) You're probably right, but make sure you look
On Thu, Apr 20, 2006 at 01:40:00AM -0400, Jacob Rus wrote:
> Easy enough: http://hcs.harvard.edu/~jrus/python/pyc-icon-variations.png
>
> Which do you prefer?
I'd say "PYC", because although it isn't a word, the icon does a
better job of connoting the file contents than any of the other words,
an
Hi again,
So that others can more easily play with these icons, here are the
Photoshop versions of the full-size glassy [logo][1], and the [document
icons][2]. All the layers are included, so it should be pretty easy to
tweak the highlights, etc. I probably won't have any more time to work
o
On 20-apr-2006, at 0:53, Christopher Barker wrote:
> Bob Ippolito wrote:
>> The libs should all be statically linked to the extensions, they
>> shouldn't be separate in the installer.
>
> Ronald Oussoren wrote:
>> I'd prefer to have fully self contained packages, and preferably
>> eggs at that. H
On 20-apr-2006, at 0:30, Jacob Rus wrote:
> Ok, what do you all think of these script and compiled script icons:
>
> PNG: http://hcs.harvard.edu/~jrus/python/python-icons-a1.png
> ZIP: http://hcs.harvard.edu/~jrus/python/python-icons-a1.zip
>
> The zip file contains icns files, png files, and als
On 20-apr-2006, at 6:16, Brendan Simons wrote:
>
> On 19-Apr-06, at 8:57 PM, [EMAIL PROTECTED] wrote:
>
>> Christopher Barker wrote:
>> > They look great, but what the heck is "DATA"?
>>
>> It was has's [idea][1] for what a .pyo/.pyc icons should look
>> like, similar to how script editor allow
90 matches
Mail list logo
