Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-list/2010-March/571010.html below:

Any downsides to UPX-ing my 32-bit Python 2.6.4 EXE/PYD/DLL files?

• Previous message (by thread): Hello,everybody,the good shoping place,the new year approaching, click in. Let's facelift bar!
• Next message (by thread): sqlite3 is sqlite 2?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Are there any downsides to UPX-ing my 32-bit Python 2.6.4
development environment EXE/PYD/DLL files?

The reason I'm asking is that I frequently use a custom PY2EXE
script that UPX's copies of these files on every build.

Yes, I could get fancy and try to cache UPXed files, but I think
a simpler, safer, and higher performance solution would be for me
to just UPX my Python 2.6.4 directory once and be done with it.

What are your thoughts?

Malcolm
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-list/attachments/20100312/bf115ea7/attachment.html>

• Previous message (by thread): Hello,everybody,the good shoping place,the new year approaching, click in. Let's facelift bar!
• Next message (by thread): sqlite3 is sqlite 2?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4