Improvements to setup script, packaging
Brought to you by:
josiahcarlson
Menu
▾
▴
#8 Improvements to setup script, packaging
I've adjusted the PyPE setup script to be able to
install PyPE as an rpm and as a standard windows
install, not just a Py2exe standalone app.
In order to do this I moved the PyPE source into a PyPE
package. I'll attach patches to the setup script and
the required changes to the package, and also a
resulting source archive.
patches to setup.py
Logged In: YES
user_id=221678
I renamed the windows script from pype.pyw to pyperun.pyw to
avoid case problems and conflicts with PyPE package
renamed pype.pyw to pyperun.pyw
Logged In: YES
user_id=221678
I also moved the following files to the PyPE subdirectory
and added an init.py:
configuration.py
parsers.py
pype.py
test_parser.py
STCStyleEditor.py
StyleSetter.py
icons and plugins subdirectory
Attached is the patch with the required changes after the
move and the new init.py
changes after moving into package
Logged In: YES
user_id=221678
Also attached the resulting tar.gz file (.zip can also be
produced) for simplicity of seeing what I've done
Just realised this should probably have gone under patches
but hopefully will be seen here...
source archive of resulting package
repackaged 2.6 tarball
Logged In: YES
user_id=221678
Rats, didn't see the 2.6 release...
I'll attach a new tarball with an updated version
This includes some fixes particular to 2.6 - you couldn't
run the setup script if it wasn't running with a DISPLAY etc
this now includes a MANIFEST.in to ensure that source
tarballs contain all the required files (and thus bdist_rpm
works)
Logged In: YES
user_id=341410
Sorry I didn't get back to you earlier. I saw the original
submission (via email) and thought "that's probably a good
idea, I'll wait until he submits all of the stuff", then
sourceforge didn't bother to send me any of your comments.
I'll attempt to merge in sufficient changes to make
everything work.
Logged In: YES
user_id=341410
I'm noticing a few issues with regards to the PyPE package
and how it expects to be run. Say, for example, in the
plugins/browser.py . Your patch presumes that the
configuration module is available via PyPE.configuration in
sys.modules. This would only be the case if PyPE was run as
'from PyPE import pype;pype.main()' or its equivalent.
Running PyPE as 'python pype.py(w)', as I would presume is
the standard method, would cause the browser, and ultimately
PyPE, to fail to load.
I'll see what I can do about getting setup.py working for
all platforms and a few other bits, but the PyPE package
seems like a gratuitous change.
Logged In: YES
user_id=341410
I haven't been able to get the bdist_wininst distutils
creation to produce anything that anyone would want to
install, so I'm explicitly removing support for it in PyPE's
setup.py. Do you know, or have you tried bdist_rpm to see
if it produces something usable? If it does anything like
the bdist_wininst does, then it is also unusable.
Logged In: YES
user_id=341410
Are the changes in PyPE 2.6.1 sufficient for your needs?
Logged In: YES
user_id=341410
Changing feature request to pending. In 7 days if the OP
does not respond, this item will be closed automatically as
presumed satisfied.
Logged In: YES
user_id=1312539
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 7 days (the time period specified by
the administrator of this Tracker).