On Fri, Sep 04, 2020 at 03:43:14PM -0500, Python wrote:
> On Fri, Sep 04, 2020 at 08:04:33AM -0800, Joshua J. Kugler wrote:
> > On Thursday, September 3, 2020 8:59:09 PM AKDT Cameron Simpson wrote:
> > > Building Python 3.8.5, running make and gcc (Debian 4.9.2-10+deb8u2)
> > > 4.9.2 I get this:
>
On Fri, Sep 04, 2020 at 08:04:33AM -0800, Joshua J. Kugler wrote:
> On Thursday, September 3, 2020 8:59:09 PM AKDT Cameron Simpson wrote:
> > I've built 3.8.5 on a few other machines happily recently.
> >
> > Building Python 3.8.5, running make and gcc (Debian 4.9.2-10+deb8u2)
> > 4.9.2 I get this
On Sat, Sep 5, 2020 at 2:06 AM Joshua J. Kugler wrote:
>
> On Thursday, September 3, 2020 8:59:09 PM AKDT Cameron Simpson wrote:
> > I've built 3.8.5 on a few other machines happily recently.
> >
> > Building Python 3.8.5, running make and gcc (Debian 4.9.2-10+deb8u2)
> > 4.9.2 I get this:
>
> I a
On Thursday, September 3, 2020 8:59:09 PM AKDT Cameron Simpson wrote:
> I've built 3.8.5 on a few other machines happily recently.
>
> Building Python 3.8.5, running make and gcc (Debian 4.9.2-10+deb8u2)
> 4.9.2 I get this:
I am going to assume the version of C required is past what is in that ol
On 04Sep2020 15:54, Chris Angelico wrote:
>On Fri, Sep 4, 2020 at 3:01 PM Cameron Simpson wrote:
>> I've built 3.8.5 on a few other machines happily recently.
>Those are warnings; if there are errors that block compilation, they
>aren't in what you quoted above.
Yes, that's what I thought. And y
On Fri, Sep 4, 2020 at 3:01 PM Cameron Simpson wrote:
>
> I've built 3.8.5 on a few other machines happily recently.
>
> Building Python 3.8.5, running make and gcc (Debian 4.9.2-10+deb8u2)
> 4.9.2 I get this:
>
> % gcc -pthread -c -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv
> -O3 -
I've built 3.8.5 on a few other machines happily recently.
Building Python 3.8.5, running make and gcc (Debian 4.9.2-10+deb8u2)
4.9.2 I get this:
% gcc -pthread -c -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3
-Wall-std=c99 -Wextra -Wno-unused-result -Wno-unused-parameter
-
from __future__ import division
from sympy import *
x, y, z, t = symbols('x y z t')
k, m, n = symbols('k m n', integer=True)
f, g, h = symbols('f g h', cls=Function)
class AA(object):
@staticmethod
def __additionFunction__(a1, a2):
return a1*a2 #Put what you want instead of
On Fri, 2 Dec 2016 01:35 pm, Ho Yeung Lee wrote:
> from __future__ import division
> import ast
> from sympy import *
> x, y, z, t = symbols('x y z t')
> k, m, n = symbols('k m n', integer=True)
> f, g, h = symbols('f g h', cls=Function)
> import inspect
Neither ast nor inspect is used. Why impor
from __future__ import division
import ast
from sympy import *
x, y, z, t = symbols('x y z t')
k, m, n = symbols('k m n', integer=True)
f, g, h = symbols('f g h', cls=Function)
import inspect
def op2(a,b):
return a*b+a
class AA(object):
@staticmethod
def __additionFunction__(a
On Thu, 1 Dec 2016 05:26 pm, Ho Yeung Lee wrote:
> import ast
> from __future__ import division
That's not actually your code. That will be a SyntaxError.
Except in the interactive interpreter, "__future__" imports must be the very
first line of code.
> class A:
> @staticmethod
> def _
import ast
from __future__ import division
from sympy import *
x, y, z, t = symbols('x y z t')
k, m, n = symbols('k m n', integer=True)
f, g, h = symbols('f g h', cls=Function)
import inspect
class A:
@staticmethod
def __additionFunction__(a1, a2):
return a1*a2 #Put what you
Hi all, how do i fix this?
$ sudo pip install lightblue
Downloading/unpacking lightblue
Downloading lightblue-0.4.tar.gz (204Kb): 204Kb downloaded
Running setup.py egg_info for package lightblue
Installing collected packages: lightblue
Running setup.py install for lightblue
Build setti
On Wed, May 19, 2010 at 8:52 PM, Steven D'Aprano
wrote:
> On Wed, 19 May 2010 22:31:31 +, Benjamin Peterson wrote:
>> Iuri gmail.com> writes:
>>> Any ideas about what is happening?
>>
>> Until Python 2.7/3.2, compile() does't like sources which don't end in a
>> newline.
It appears to be thi
Steven, it works fine to some cases.
I have problem only when last line is a comment and before it I have an
indentation. It is a specific case, and it is not a common case.
>>> compile("for i in [1,2,3]:\n pass\n#end", "test_file.py", "exec")
What I understanded about Benjamin's answer is compi
On Wed, 19 May 2010 22:31:31 +, Benjamin Peterson wrote:
> Iuri gmail.com> writes:
>> Any ideas about what is happening?
>
> Until Python 2.7/3.2, compile() does't like sources which don't end in a
> newline.
Are you sure about that?
>>> x = compile("print __import__('sys').version, 'see
Thanks, Benjamin.
I used Python 2.6 to these tests.
[]s
iuri
On Wed, May 19, 2010 at 7:31 PM, Benjamin Peterson wrote:
> Iuri gmail.com> writes:
> > Any ideas about what is happening?
>
> Until Python 2.7/3.2, compile() does't like sources which don't end in a
> newline.
>
>
>
> --
> http://m
Iuri gmail.com> writes:
> Any ideas about what is happening?
Until Python 2.7/3.2, compile() does't like sources which don't end in a
newline.
--
http://mail.python.org/mailman/listinfo/python-list
>>> compile("for i in [1,2,3]:\n pass\n#end\n", "test_file.py", "exec")
at 0x266a378, file "test_file.py", line 1>
>>> compile("for i in [1,2,3]:\n pass\n#end", "test_file.py", "exec")
Traceback (most recent call last):
File "", line 1, in
File "", line 2, in cptest
File "test_file.py", line 3
#e
Jimbo wrote:
> Can you help me figure out why I am getting this compile error with my
> program. The error occurs right at the bottom of my code & I have
> commented where it occurs.
[...]
> def main():
> programEnd = False;
>
> while (programEnd == False):
>
Jimbo a écrit :
Hello
Can you help me figure out why I am getting this compile error with my
program. The error occurs right at the bottom of my code & I have
commented where it occurs.
The error is:
[QUOTE]Expected an indented block[/QUOTE]
[CODE]
(snip)
# Main program loop
def
Hello
Can you help me figure out why I am getting this compile error with my
program. The error occurs right at the bottom of my code & I have
commented where it occurs.
The error is:
[QUOTE]Expected an indented block[/QUOTE]
[CODE]"""
*Stock Data Builder*
Algorithm:
On Saturday 28 October 2006 06:42, [EMAIL PROTECTED] wrote:
> here is th output :
>
> [EMAIL PROTECTED] PyQt-x11-gpl-3.16]# python configure.py -q
> /usr/lib/qt-3.3/ -w
[...]
> Checking to see if the qtcanvas module should be built...
> /usr/bin/ld: cannot find -lXext
> collect2: ld returned 1
Hi David
here is th output :
[EMAIL PROTECTED] PyQt-x11-gpl-3.16]# python configure.py -q
/usr/lib/qt-3.3/ -w
This is the GPL version of PyQt 3.16 (licensed under the GNU General
Public
License) for Python 2.4.2 on linux2.
Type 'L' to view the license.
Type 'yes' to accept the terms of the licens
[EMAIL PROTECTED] wrote:
> [EMAIL PROTECTED] PyQt-x11-gpl-3.16]# python configure.py -q
> /usr/lib/qt-3.3/
> This is the GPL version of PyQt 3.16 (licensed under the GNU General
> Public
> License) for Python 2.4.2 on linux2.
[...]
> Creating features file...
> Error: Unable to build mkfeatures u
[EMAIL PROTECTED] PyQt-x11-gpl-3.16]# python configure.py -q
/usr/lib/qt-3.3/
This is the GPL version of PyQt 3.16 (licensed under the GNU General
Public
License) for Python 2.4.2 on linux2.
Type 'L' to view the license.
Type 'yes' to accept the terms of the license.
Type 'no' to decline the terms
Title: RE: MySQLdb compile error with AMD64
Found it.
Had to change
Extra_compile_args = config(cflags) to the actual list with –march=athlon64
Now just realized that I didn’t download the right RPMs for MySQL for SUSE on AMD64 (so got lib errors I am assuming cos of that).
Will download
Title: MySQLdb compile error with AMD64
>> Can anyone offer any assistance on this one?
>
>Look here:
>
>>> gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -fmessage-length=0 -Wall
>>> -D_FORTIFY_SOURCE=2 -g -fPIC -I/usr/include/mysql
>>&g
[EMAIL PROTECTED] wrote:
> Can anyone offer any assistance on this one?
Look here:
>> gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -fmessage-length=0 -Wall
>> -D_FORTIFY_SOURCE=2 -g -fPIC -I/usr/include/mysql
>> -I/usr/include/python2.4 -c _mysql.c -o
>> build/temp.linux-x86_64-2.4/_mysql.o -I
Can anyone offer any assistance on this one?
Is it unsupported on AMD64 ? Nothing in the README points to that. I
thought it would default to 32bit if not supported under 64.
>
> Hi,
>
> I have been using MySQLdb on a 32-bit processor, no worries. Love it.
>
> I went to install on an AMD64 runn
Hi,
I have been using MySQLdb on a 32-bit processor, no worries. Love it.
I went to install on an AMD64 running the 64-bit version of SUSE 10.0.
I get the following error during the "python setup.py build"
gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -fmessage-length=0 -Wall
-D_FORTIFY_SOURCE
31 matches
Mail list logo
