A while ago, when I wanted to write a new test that required some programming, I wrote it in Python because it's more commonly available, generally more user friendly, easier to read, etc. I forgot to document the new dependency. I've fixed that now.
In the long run I hope to rewrite the existing build-time Perl code into Python, but it's not a priority. On Mon, Nov 19, 2018 at 11:08:10AM +0100, John Darrington wrote: > A dependency on python (of any version) is something completely new to > me. Why are we dependent on that? When did it happen? > > J' > > On Sun, Nov 18, 2018 at 01:11:15PM -0800, Ben Pfaff wrote: > On Sun, Nov 18, 2018 at 01:53:08PM +0100, Friedrich Beckmann wrote: > > Hi Ben, > > > > the spread-sheet-widget is in debian unstable! > > > > https://tracker.debian.org/pkg/spread-sheet-widget > > I did a build with pbuilder, with the intention of uploading. The build > fails because python is not available. It looks like python3 is getting > installed but not python2, and that only python2 is available by the > name "python". I guess that PSPP should learn to work with python3, but > for now it's probably easiest to add a build dependency on python2. > > Thanks, > > Ben. > > _______________________________________________ > pspp-dev mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/pspp-dev > > -- > Avoid eavesdropping. Send strong encrypted email. > PGP Public key ID: 1024D/2DE827B3 > fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3 > See http://sks-keyservers.net or any PGP keyserver for public key. > _______________________________________________ pspp-dev mailing list [email protected] https://lists.gnu.org/mailman/listinfo/pspp-dev
