> > See the steps I mentioned. Unless step #1 is completed there is no way
> > to make the following code work:
> >
> > open(Path("foobar"))
> >
> > Well, there is one alternative which is:
> >
> > open(Path("foobar").tostring())
> >
> > And that is a Java-esque workaraound that I think noo
"Steve Holden" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> You may be aware that Tim Parkin's work on our "next-generation" web
> presence has borne fruit in the shape of beta.python.org. While there's
> still a lot to be done Tim has given us a great start by creating a
> frame
Stephen J. Turnbull:
> Jason> Filesystem paths are in fact strings on all operating
> Jason> systems I'm aware of.
>
> I have no idea what you could mean by that. The data structure used
> to represent a filesystem on all OS filesystems I've used is a graph
> of directories and files. A
Andrew Pinski wrote:
> Does phython already use autoconf? I think it does, if so then there
> should be no issues.
Yes, but your conclusion is wrong. Python uses autoconf, but not
aclocal/automake. The generated configure is explicitly not covered by
the GPL; the status of the generated aclocal.
Fredrik Lundh wrote:
> instead of spending more time and creativity on a sourceforge account
> that's only used for tracking, how about moving the trackers to python.org ?
That's an old plan. It failed so far because no volunteer ever appeared
to make it happen (actually, some did appear, but didn
On 28/01/2006, at 10:41 AM, Martin v. Löwis wrote:
> You misunderstand the GPL. Section 2b) is pretty clear that any
> application that contains GPL-licensed code must be, itself,
> distributed
> under the terms ofthe GPL
Quite so, but using the autotools does NOT include any GPL code in
the r
> "Martin" == Martin v Löwis <[EMAIL PROTECTED]> writes:
Martin> Instead, it means we need a build process for libffi which is
Martin> independent of autoconf (or convince the authors of aclocal.m4 to
Martin> relicense it, but that is likely futile).
Martin> As a matter of fact, Python itself
On Jan 27, 2006, at 1:32 PM, Thomas Heller wrote:
>
> I guess I understood this already. The difference to the C
> compiler is
> that the compiler is not 'bundled' with Python, it is installed
> separately.
>
> Can anyone of the python-dev core team comment: can we live with
> the GPL
> licen
> "Giovanni" == Giovanni Bajo <[EMAIL PROTECTED]> writes:
Giovanni> This would be a new interpretation of the license. The whole
Giovanni> autotools chain is GPL and it is used on way too many
Giovanni> programs which are not GPL. They're so many I won't even
Giovanni> mention one. Anyway, IAN
On Fri, 2006-01-27 at 18:03 +0100, Thomas Heller wrote:
> [I've added python-dev to cc:]
>
> Anthony Green <[EMAIL PROTECTED]> writes:
>
> > On Fri, 2006-01-27 at 17:08 +0100, Thomas Heller wrote:
> >> Anyway, another question is: Is aclocal.m4 needed at all for building
> >> (or maybe for regene
BJörn Lindqvist <[EMAIL PROTECTED]> writes:
> [M.-A. Lemburg]
>> I don't see why this is critical for the success of the Path
>> object. I agree with Thomas that interfaces should be made
>> compatible to Path object.
>
> See the steps I mentioned. Unless step #1 is completed there is no way
> to
Ronald Oussoren wrote:
> You have a point there. I'm not entirely convinced though, the argument
> that Python would be a derived work of libffi's aclocal.m4 when libffi
> were included in the Python repository seems very weak to me.
The GPL says "contains or is derived from". Clearly, "identifia
Martin v. Löwis wrote:
> Sorry, no HTML allowed there.
>
> I created a support request to change/remove the button at
>
> http://sourceforge.net/tracker/index.php?func=detail&aid=1417298&group_id=1&atid=21
instead of spending more time and creativity on a sourceforge account
that's only used
Thomas Wouters wrote:
> I'd need developer access back to check it in, though. Unless anyone
> objects, of course :)
I copied ~/thomas/authorized_keys to ~pythondev/keys/thomas.wouters,
changed ownership/permissions, and ran make_authorized_keys in the
pythondev account. So you should have access
On 28-jan-2006, at 0:53, Martin v. Löwis wrote:
Ronald Oussoren wrote:
Merging the two configure files might be a good idea anyway, that
would
take away the need to run configure from setup.py. IANAL, but I
don't
quite get how a GPL'd support script, if there is such a thing,
in the
b
Stephen J. Turnbull wrote:
> Jason> Filesystem paths are in fact strings on all operating
> Jason> systems I'm aware of.
>
> I have no idea what you could mean by that. The data structure used
> to represent a filesystem on all OS filesystems I've used is a graph
> of directories and file
Nick Coghlan wrote:
> Is it possible to make that URL a hyperlink?
No, all HTML gets stripped/quoted as text.
> " The Python programming language, an object-oriented scripting and rapid
> application development language.
> Despite what the green button below says, you can NOT download it
> dir
Bill Northcott wrote:
> Quite so, but using the autotools does NOT include any GPL code in the
> resulting program.
Hmm. Please take a look at
http://cvs.sourceforge.net/viewcvs.py/*checkout*/ctypes/ctypes/source/gcc/libffi/aclocal.m4?rev=1.1.4.1
This file contains a large number of licensing t
18 matches
Mail list logo
