[04:03:02] [connected at Fri Mar 10 04:03:02 2006]
[04:03:02] <> *** Looking up your hostname...
[04:03:02] <> *** Checking ident
[04:03:03] <> *** Found your hostname
[04:03:33] <> *** No identd (auth) response
[04:03:33] <> *** Your host is zelazny.freenode.net[zelazny.freenode.net/6667], running version hyperion-1.0.2
[04:03:33] [I have joined #peak]
[12:02:13] ** pje has joined us
[15:14:41] ** whit has joined us
[15:44:42] whit is now known as whit|talk
[16:36:21] ** cogumbreiro has joined us
[16:36:23] <cogumbreiro> lo all
[16:36:27] <cogumbreiro> pje, u there?
[16:37:53] ** whit|talk has left IRC ()
[16:39:53] <cogumbreiro> when using setuptools is there any way to generate an win32 installers that works with setuptools installations (generates the executable and whatnot)?
[16:43:44] ** whit has joined us
[17:37:03] ** whit has left IRC ()
[18:13:04] ** whit has joined us
[18:13:13] ** whit has left IRC (Client Quit)
[18:44:36] <pje> cogumbreiro, yes.
[18:44:51] <pje> bdist_winist
[18:45:02] <pje> er, bdist_wininst
[18:45:18] <pje> if you do it on a setuptools-using package, you get one with an egg inside
[18:45:52] <cogumbreiro> hmm
[18:45:53] <cogumbreiro> strange
[18:46:06] <pje> how so?
[18:46:11] <cogumbreiro> I have a setuptools package and it's not creating the setuptools friendly installer
[18:46:23] <pje> what version of setuptools are you using?
[18:46:25] <cogumbreiro> I am generating it from linux
[18:46:29] <pje> oh
[18:46:34] <pje> I've never tried that.  :)
[18:46:38] <pje> only on Windows
[18:46:46] <pje> still, what version of setuptools do you have?
[18:46:46] <cogumbreiro> oh... :(
[18:47:08] <cogumbreiro> setuptools-0.6a10dev_r41995
[18:47:22] <cogumbreiro> isn't there a way to do it from Linux?
[18:48:21] <pje> dunno
[18:48:59] <pje> r41692 added roundtripping of eggs in .exe files 
[18:49:17] <pje> What does bdist_wininst do?
[18:49:28] <cogumbreiro> creates a package as if there was no setuptools
[18:49:41] <cogumbreiro> if I have two packages it will just put them on site-packages
[18:49:45] <pje> Does the package import setuptools?
[18:50:08] <cogumbreiro> on setup.py?
[18:50:09] <cogumbreiro> yes
[18:50:11] <pje> note that the created .exe should install an .egg-info subdirectory alongside the package
[18:50:14] <cogumbreiro> I can create eggs with it
[18:50:30] <pje> and that's all setuptools needs to recognize the installed package
[18:51:36] <cogumbreiro> it doesn't put the .egg-info inside the installer
[18:51:47] <cogumbreiro> and nor do the created scripts work
[18:54:17] <pje> well, you might try upgrading setuptools
[18:55:01] <pje> r42345 has some fixes for script issues that might relate
[18:56:26] <cogumbreiro> cool, I will then
[18:56:40] <pje> And I just tried that revision on Linux and built a setuptools win32.exe installer
[18:57:13] <pje> and it has the .egg-info at least
[18:58:08] <pje> although I suspect the scripts are hosed
[18:58:43] <cogumbreiro> nice, I will update it in a few mins and tell you how it went
[18:58:46] <pje> it looks like setuptools builds the scripts as if you were on Linux, rather than win32
[18:58:47] <cogumbreiro> thx :)
[18:58:55] <cogumbreiro> yes
[18:59:01] <cogumbreiro> the script has no 'py' extension
[18:59:07] <cogumbreiro> at least my version
[18:59:16] <pje> more precisely, the script has no -script.py and .exe
[18:59:31] <cogumbreiro> exactly
[19:00:10] <pje> so, it doesn't support cross-compiling scripts for bdist_wininst
[19:00:23] <pje> Guess I should add that to my bug list.  :)
[19:00:30] <cogumbreiro> Cool :)
[19:00:44] <cogumbreiro> so meanwhile I have to create the wininst on windows, right?
[19:00:50] <pje> Doesn't mean it'll ever get *done*.  :)
[19:00:57] <pje> yes
[19:01:08] <cogumbreiro> is it difficult to do?
[19:01:14] <cogumbreiro> I could do it and send u the patch
[19:01:17] <pje> ironically enough, if you use easy_install and point it at the broken .exe, it will turn it into a valid egg
[19:01:34] <cogumbreiro> 'point it' how?
[19:01:36] <pje> the fix would be difficult, yes, because currently setuptools doesn't patch bdist_wininst
[19:01:44] <cogumbreiro> ah
[19:01:47] <pje> easy_install /path/or/url/to/.exe
[19:02:03] <pje> EasyInstall can turn bdist_wininst .exe's back into eggs
[19:02:17] <cogumbreiro> bug eggs aren't double clickable... :(
[19:02:22] <pje> and it'll fix the scripts in the process, because it rebuilds them.
[19:02:48] <pje> You could set up a shell association from .egg to EasyInstall.  ;)
[19:02:50] <cogumbreiro> if .egg extension was registred under windows it would be great
[19:03:19] <pje> You wouldn't even need a program for that, since EasyInstall already exists.  Just a .reg file would do the trick.  :)
[19:04:05] <pje> In fact, there's an easy_install.exe, though you might want to make a .pif so the console window stays open when it finishes running.
[19:05:27] <pje> Or perhaps I could add an option that tells easy_install to stay running and wait for a keypress, although that wouldn't work for errors.  :)
[19:06:00] <cogumbreiro> yes, it would be a problem...
[19:06:03] <pje> Would be kind of nice, though, in that people could then just click on eggs in their web browsers to install them.
[19:07:18] <cogumbreiro> exactly
[19:07:39] <cogumbreiro> windows users are always spoilled :P
[19:08:03] <pje> Ooh, no need for a .pif...  just use "cmd /K easy_install blah blah..."
[19:09:08] <cogumbreiro> for what?
[19:09:34] <pje> to run it from the extension
[19:09:42] <pje> oh wait, I think that leaves you with a command prompt...
[19:10:17] <pje> Although that may not be such a bad thing.
[19:10:58] <pje> Anyway, it looks like you could just set up a default shell action for "Install Python Egg" that runs "cmd /D /K easy_install %s"
[19:11:12] <cogumbreiro> and how would one register that?
[19:11:14] <pje> modulo a few issues for the exact location of easy_install.exe
[19:11:31] <pje> Well, you can do it by hand in Windows Explorer - under Folder Options, File Types
[19:11:31] <cogumbreiro> yes, python24/scripts would need to be on the PATH
[19:11:55] <pje> You could just put C:\Python24\Scripts\easy_intall.exe in there.
[19:12:27] <pje> But everything needed to define it should also be definable as a .reg file
[19:12:54] <pje> For that matter, I could create an easy_install command that could do the registration itself by modifying the registry
[19:13:22] <pje> Although it'd probably be better to make a separate command for that.
[19:13:46] <cogumbreiro> yes, maybe
[19:13:48] <pje> like "wineggs" or something.
[19:13:53] <cogumbreiro> :)
[19:13:57] <pje> or eggreg  :)
[19:17:52] <cogumbreiro> eheh
[19:21:02] <pje> Hm, I've almost got it working, but it uses short (8.3) filenames instead of long filenames, which then doesn't work so well
[19:23:24] <cogumbreiro> :S
[19:29:57] <pje> Sweet...  you just have to use %L
[19:33:51] <pje> Here's the .reg file:
[19:33:52] <pje> Windows Registry Editor Version 5.00
[19:33:52] <pje> [HKEY_CLASSES_ROOT\.egg]
[19:33:52] <pje> @="Python.Egg"
[19:33:52] <pje> [HKEY_CLASSES_ROOT\Python.Egg]
[19:33:52] <pje> "EditFlags"=dword:00000000
[19:33:54] <pje> "BrowserFlags"=dword:00000008
[19:33:56] <pje> @="Python Egg"
[19:33:58] <pje> "AlwaysShowExt"=""
[19:34:00] <pje> [HKEY_CLASSES_ROOT\Python.Egg\DefaultIcon]
[19:34:02] <pje> @="C:\\Python23\\python.exe,0"
[19:34:04] <pje> [HKEY_CLASSES_ROOT\Python.Egg\shell]
[19:34:06] <pje> @="Install Egg for Python 2.3"
[19:34:08] <pje> [HKEY_CLASSES_ROOT\Python.Egg\shell\Install Egg for Python 2.3]
[19:34:10] <pje> [HKEY_CLASSES_ROOT\Python.Egg\shell\Install Egg for Python 2.3\command]
[19:34:12] <pje> @="c:\\windows\\command\\cmd.exe /D /K C:\\Python23\\Scripts\\easy_install \"%L\""
[19:34:20] <pje> Feel free to modify to suit.  :)
[19:34:49] <pje> Should be interesting to see if you can browse the cheeseshop and click on eggs with that.
[19:36:28] <cogumbreiro> thanks alot! :)
[19:40:04] <pje> This should be especially good with the latest setuptools, which can handle conflicts without needing any command line options.
[19:40:26] <pje> (latest = what I just checked in 30 seconds ago, r42965
[19:41:03] <pje> Interestingly, you can also go browse your site-packages and double-click on eggs to change which version is active.  :)
[19:41:21] <pje> Although I suspect it won't work right for directory eggs.
[21:21:54] ** pje has left IRC ("Client exiting")
[21:35:58] ** DesreveR has joined us
[21:51:07] ** r0nny has left IRC (Read error: 110 (Connection timed out))
[22:06:45] ** cogumbreiro has left us