[00:36:01] ** bitmvnch has left IRC () [04:59:23] [connected at Wed Jul 19 04:59:23 2006] [04:59:23] <> *** Looking up your hostname... [04:59:23] <> *** Checking ident [04:59:23] <> *** No identd (auth) response [04:59:24] <> *** Found your hostname [04:59:24] <> *** Your host is zelazny.freenode.net[zelazny.freenode.net/6667], running version hyperion-1.0.2 [04:59:24] [I have joined #peak] [07:32:26] ** bitmvnch has joined us [10:04:07] ** fincher has joined us [10:04:24] anyone seen pje recently? [10:13:54] ** whit has joined us [12:04:08] ** pje has joined us [13:25:08] whit is now known as whit|out [13:25:58] ** whit|out has left IRC () [13:34:28] ** ErikRose has left IRC () [13:48:21] ** coderanger_ has joined us [13:48:54] ** bitmvnch has left IRC () [13:50:43] pje: can you verify that setuptools requires Python 2.4 on x86-64 systems to work properly? [13:51:09] I'm not sure I understand the question. [13:51:20] Are you asking me whether the docs are correct in stating that requirement? [13:51:39] pje: I'm asking whether I'm correct in my understanding that the documents state that requirement :) [13:51:52] Yes, they do, and yes, you are. :) [13:52:09] excellent. Any known workaround for systems that might, for some reason or another, be stuck with Python 2.3 for the time being? [13:52:17] Yes - you can use uncompressed eggs. [13:52:34] And setuptools actually generates uncompressed eggs for Python 2.3, in order to work around it. [13:52:38] given a compressed egg, is there an easy way to extract an uncompressed egg? [13:52:50] unzip? [13:52:52] Most eggs built for 2.3 are uncompressed. [13:53:05] But it's possibly you might encounter a really old egg that's not. [13:53:15] As long as you build your own eggs with Python 2.3, they'll be uncompressed. [13:53:26] ok. [13:53:47] Alternately, you can configure easy_install to install eggs unzipped. [13:54:05] after I build such an egg, I'm left with a .egg file and a .egg-info directory. Is there anything I'm supposed to do with the latter? [13:54:05] But basically I just went ahead and made setuptools create uncompressed eggs when run on Python 2.3. [13:54:36] The .egg-info directory is what gets used to get your metadata if you run the code from your source directory. [13:54:55] It gets regenerated whenever you run setup.py develop, sdist, bdist_egg, or test. [13:55:23] you can also manually add files to it, and they'll get zipped up and shipped with your egg, where they'll be readable using the pkg_resources metadata API [13:55:34] pje: yeah, I'd run "python setup.py bdist_egg". To install that egg, I just copied it to /usr/lib/python2.3/site-packages. Do I need to do anything similar with the .egg-info file? [13:55:56] no. [13:56:16] If you want to install an egg, btw, just run "setup.py install" - that will build the egg and install it properly. [13:56:28] ah, cool. [13:56:35] Right now, you can only use the egg if you use a 'require()' call, because it's not on sys.path, despite being in site-packages. [13:56:41] oddly enough, today's the first day I've ever worked with eggs :) [14:02:04] ** ErikRose has joined us [14:14:47] ** bitmvnch has joined us [14:24:44] ** bitmvnch has left IRC () [15:18:09] ** whit_ has joined us [15:34:08] ** ErikRose has left IRC () [15:51:51] ** coderanger_ has left IRC (Read error: 110 (Connection timed out)) [15:59:24] ** ErikRose has joined us [17:11:26] ** coderanger_ has joined us [17:50:48] ** whit has joined us [18:03:29] ** whit_ has left IRC (Read error: 110 (Connection timed out)) [18:04:10] ** whit_ has joined us [18:15:31] ** whit has left IRC (Read error: 110 (Connection timed out)) [19:01:05] whit_ is now known as whit [19:49:29] ** bitmvnch has joined us [20:03:43] ** coderanger_ has left IRC ("->Job #4") [20:40:14] ** pje has left IRC ("Client exiting") [22:22:56] ** coderanger_ has joined us [23:06:10] ** bitmvnch has left IRC () [23:17:31] ** coderanger_ has left IRC (Read error: 110 (Connection timed out))