packaging

I hope my title was clear. I'm using wxpython for making a GUI and I want it to be able to be opened, extracted, and have it work on all operating systems. I was able to include twill by finding a folder called twill inside the twill archive, which worked fine. However, I'm unable to figure out how to correctly package wxpython. EDIT: I'm not using either. py2exe is only for windows, and bbfreeze doesn't seem to work on mac (so it's not cross platform) Unfortunately, there's just no one stop solution so that a single installable executable will work across all operating systems. The right

I come with the background in languages like Java or Python where modular programming is enabled by packaging system and import directive (aka namespace aliasing). Historically MATLAB's approach to resolve problems like naming conflicts boils down to setting/playing with MATLABPATH, renaming/extending identifiers with prefixes, etc. So far I have been successfully playing with native MATLAB packaging by prepending plus sign "+" before the folder name (MATLAB notation for package also see here ). Obviously they are very long to type ;-) Basically I am back to the similar problem as discussed

I've created a little Windows app that uses the ImageMagick C API but have run into a bit of a brick wall. The app works fine and I'm ready to share it with a few others in our organisation but I can't find documentation on distributing such an app without installing ImageMagick on the target machine. Does anyone here have information, or a link to information, that details how to package this up for distribution? What DLLs are required and which one(s) need to registered with Windows? The target users will be on a mix of XP and Win7. I had to do something similar, though I built Imagemagick

I want to distribute a custom matplotlib style sheet , but right now the only way I can think of is uploading it to Gist or some other website and tell my users to manually download it to some configuration directory. Is there a way to distribute a style sheet as if it were a Python package, or as part of a module? Something easy like pip install mpl_fancy . After reading the link from @aloctavodia and consulting the massmutual/mmviz-python GitHub repo , this is what I came up with. setup.py from setuptools import setup from setuptools.command.install import install import os import shutil

I've run into interesting problem which is absolutely new to me. As I've suddenly discovered, Jar specification says that, being included, META-INF and MANIFEST.MF must be first and second entries of *.jar package and not just directory and file within archive. I'm working with Java framework being very watchful about this requirement and not as much verbose. How do I check that META-INF and MANIFEST.MF are properly ordered within jar? UPDATE: Many of jars are third-party, and there are many of them. I'm not able to open these jars in notepad, excel, hexeditor, photoshop or whatever looking

I managed to use this react-hot-boilerplate configuration script to create and test a simple React Flux webapp. Now that I have a website I like when I run npm start , what would be the easiest/best way to add a production build in the configuration? When I use that 'package' command I would like to get a little prod folder with all the final html and minified js files that I need in it, is that what I should expect? This is my package.json : { "name": "react-hot-boilerplate", "version": "1.0.0", "description": "Boilerplate for ReactJS project with hot code reloading", "scripts": { "start":

I've got a large project on my hand (master) that is split into several components (liba, b, c, d) to ease building and maintenance. When building the whole package, all of the subcomponents must be built in sequence, and some of these packages depend upon each other. In more explicit terms, liba is a prerequisite for b, c and d, and the presence of liba is checked by the configure script. This check is definitely necessary to give user-friendly error messages when building the b distribution on its own. However, when building the master package and all its subpackages, liba is built as a