Dusty
> In all honesty, I don't know how to do that from inside the installer.
> I'll look into it for the next release. This is indeed done
> automatically if you use the setup.py in a source release, although it
> seems under Windows you have to run the installer twice
...
> The issue here is that I have very little experience deploying Python
> apps on Windows. The last program I released for Windows was written
> in Visual Basic five. 
...
> I dont have installed Python24 on C: and also, share dir was created on my
> python directory.
> changing the value of share your editor works.
...
···
---
In my mind, your application is suffering from a HUGE design mistake. It requires
an installer (based on distutils) and this installer will install the application
in the ..\site-packages directory. This is not the right place for users Python
scripts, even if the user is the script developer. This directory is not a repository
for Python scripts, but a place for "modules" extending the core Python.
I strongly suggest, you reorganize the dir mismatch in your application, is such
a way pallavi can be started from everywhere. You may take a look at the various
editors and check how this is realized. Basically, all Python scripts using subdirs
have something similar to this in their main function:
def main():
#home applicatin dir
path = os.path.abspath(sys.argv[0])
dirname, basename = os.path.split(path)
#miscellaneous utilities dirs
pallavidir = os.path.join(dirname, 'pallavi')
configdir = os.path.join(dirname, 'config')
pluginsdir = os.path.join(dirname, 'pluginsdir')
imagesdir = os.path.join(dirname, 'images')
lexersdir = os.path.join(dirname, 'lexers')
print 'Dir of the application: %s' % dirname
print 'Name of the applications: %s' % basename
print 'pallavi subdir : %s' % pallavidir
print 'config subdir: %s' % configdir
print 'plugins subdir: %s' % pluginsdir
print 'images subdir: %s' % imagesdir
print 'lexers subdir: %s' % lexersdir
A good Python script can be copied (not installed) on a usb-key (eg) and it can be
launched from there. So does the wxPython demo.
If your application should be installed on a multiusers platform (*x or
Windows) and it should use user specific config, you may consider
wx.StandardPaths.
======
Chris
> OK, I have to ask -- Why yet another wxPython-based Text editor?
> There is PyPE, SPE, UliPad, Peppy, DrPython, .....
Do you know the common point between PyPE, Ulipad, DrPython?
They all do not work on my Win box (Swiss French keyboard), and as I know
where the problem is coming from, I can tell you they will not work properly
on any Western European user platform... (This was my main reason for testing
pallavi).
PyShell is sometimes suffering from the same issue, I take the time to check it at every new release and propose a correction if necessary. I cann't do that for
every piece of wxPython code.
Jean-Michel Fauth, Switzerland