RE: [Pythoncard-users] Python distribution problems

[Schollnick, B. <Ben...@xe...>]

> >I am unclear on what you are suggesting they are basing=20
> their decisions=20
> >on?  (The quote does not include it)  Presumably on the fact=20
> >need to instead Python, WxPython, and PythonCard?  Windows=20
> programmers=20
> >are fully aware of dependencies...  .Net anyone?

> True - they are aware of them - but that doesn't mean they=20
> like them. I=20
> think it would be pretty cool to have the *option* of a=20
> single download=20
> and install to do Python, wxPython and Pythoncard in one easy=20
> operation.=20
> I have no idea how easy it would be to create that - but I suspect it=20
> would overcome some people's concerns about the complexity of getting=20
> started with Pythoncard.

The option might be nice....  But is it a reasonable option?

That's at least 6+ different archives.... (Windows, *Nix, MacIntosh) ...
That Kevin would have to maintain.  I don't even know if Kevin has all
of those systems....

Plus just python alone (without Source code) is 10 MB.  And that's a
dedicated installer (.MSI)....  It will be larger in this combined
installer....  WxPython is another 6 MB, and PythonCard is another 2...

SubTotal roughly 20Mb.

That is not including Python Source code, nor Win32 Extensions...
And is consists of 3 different installers....

1) This will be at least a 20 Mb download....
2) Who is liable for this?  If a problem occurs with <fill in the blank>
	is Kevin going to be forced to Fix it?  (WxPython Developer:
It's=20
	not a bug in our code, your installer goofed...)
3) How is all of this going to be packaged?  We have a .MSI installer,
	two .EXE installers...  Prepackage/ZIP everything up?  What if
	the person installing wants a non-standard path or library?

It maybe a good idea, but I think it is safer and smarter to use=20
approved installers directly from the authors...

A better suggestion, IMHO, is to suggest to Kevin to have a quick link
at the top pointing to each installer... =20

ie.
-----------------------------------------------------------------
PythonCard is currently at Version v0.81. =20

Pythoncard requires the following software:

	* Python v2.3.x or later
	  Tested with Version v2.3.888 (download Installer) on xx/xx/xx

	* WxPython v2.x.x or later (Unicode and Non-Unicode versions)
	  Tested with Version v2.3.888 (download Installer) on xx/xx/xx

-------------------------------------------------------------------

Each development environment is going to be different, some people will
want WxPython with Unicode support, some without...  Some will need
WxPython vxx.yy.zz and some want to be using the CVS nightly builds...

There is no sensible way to allow of that to be bundled without a huge
amount of effort.

		- Benjamin