On <some multitude of times>, CM <cmpyt...@gmail.com> wrote: > What I was thinking of was that if you are going to sell software, you want > to make it as easy as possible, and that includes not making the potential > customer have to install anything, or even agree to allow you to "explicitly" > install a runtime on their computer. If the potential customer just sees, > clicks, and installs, that should be the most they ought to have to do.
I don't really get what you are saying. Do you, or do you not, want it installed? > Also, many programs rely on 2-3 dependencies, and sometimes that is asking a > lot of the end user to install. (I know, I know, it shouldn't be...and with > things like pip it really shouldn't be, but you know how it goes). > >> I responded (to some parts): >> But why do they need to install it at all? If you're not installing >> the .py file, then just include those dependencies in the archive -- >> .py files are tiny. If you are installing the .py with a setup.py >> (like with the link I included), then just install them at the same >> time. > > Maybe. I'll have to think about it. I'm referring to libaries as > dependencies. So for example, though .py files are small, wxPython, for > example, isn't tiny, nor are other libraries one might use. Please excuse the fact I haven't done anything serious on Windows in years so I'm not really sure what I'm saying. How does Windows deal with dependencies? It's going to have to be fetched at one point anyway, so that's either at download-time, install-time or run-time. The first lets you just add it to the archive, the second lets you deal with it through a good standard distribution manager thing, the third is potentially crazy. Hence, wutz za probem bruv? -- http://mail.python.org/mailman/listinfo/python-list
