On Jun 13, 2013, at 6:18 AM, Christian Stimming <christ...@cstimming.de> wrote:
> Am Mittwoch, 12. Juni 2013, 17:27:38 schrieb Rand Batchelder: >> The python bindings were never enabled for the windows binaries previously. >> >> Will the python bindings be enabled for the windows binaries in ver 2.5 ? > > No, they will not. > > The previous answer by David T. says it all: > >> My understanding about why the Windows and Mac builds skip installing >> Python is that these OSes do not consistently provide Python to users. >> Including it by default in GnuCash for these platforms would require >> GnuCash to include Python in the distribution, with concomitant file size >> problems and requiring GnuCash to keep an updated Python. > > in other words, the gnucash windows binary with its current 70MB would have > to > grow even more to contain one complete python binary (and not only its > gnucash > bindings) with the correct version that fits the version that is used by the > build server to build the python gnucash bindings. Current python installers > come at 20MB size. We won't do that. > > But feel free to provide a build script and/or a separate binary package that > adds the bindings to an existing gnucash package... There's got to be a way around that. Pybsddb [1] makes a module that connects multiple versions of Berkeley DB with any version of Python after 2.3. What are they doing differently from us? Regards, John Ralls [1] http://www.jcea.es/programacion/pybsddb.htm _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
