[ python-Bugs-1644239 ] Error arrow offset wrong
Bugs item #1644239, was opened at 2007-01-25 09:51 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1644239&group_id=5470 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: IDLE Group: Python 2.4 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Cees Timmerman (ctimmerman) Assigned to: Nobody/Anonymous (nobody) Summary: Error arrow offset wrong Initial Comment: >>> def check_path(f): ... asert not '"' in f File "", line 2 asert not '"' in f ^ SyntaxError: invalid syntax It looks like the tab i used to indent was converted to 4 spaces and then each space back to tabs which each got converted to 4 spaces. Python 2.4.4c1 (#2, Oct 11 2006, 21:51:02) [GCC 4.1.2 20060928 (prerelease) (Ubuntu 4.1.1-13ubuntu5)] on linux2 -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1644239&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1637120 ] Python 2.5 fails to build on AIX 5.3 (xlc_r compiler)
Bugs item #1637120, was opened at 2007-01-16 18:06
Message generated for change (Comment added) made by oirraza
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1637120&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Build
Group: Python 2.5
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Orlando Irrazabal (oirraza)
Assigned to: Thomas Heller (theller)
Summary: Python 2.5 fails to build on AIX 5.3 (xlc_r compiler)
Initial Comment:
Initial Comment:
Build of Python 2.5 on AIX 5.3 with xlc_r fails with the below error message.
The configure line is:
./configure --with-gcc="xlc_r -q64" --with-cxx="xlC_r -q64" --disable-ipv6
AR="ar -X64"
[...]
building '_ctypes' extension
xlc_r -q64 -DNDEBUG -O -I. -I/sw_install/python-2.5/./Include
-Ibuild/temp.aix-5.3-2.5/libffi/include -Ibuild/temp.aix-5.3-2.5/libffi
-I/sw_install/python-2.5/Modules/_ctypes/libffi/src -I./Include -I.
-I/sw_install/python-2.5/Include -I/sw_install/python-2.5 -c
/sw_install/python-2.5/Modules/_ctypes/_ctypes.c -o
build/temp.aix-5.3-2.5/sw_install/python-2.5/Modules/_ctypes/_ctypes.o
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 221.3: 1506-166 (S)
Definition of function ffi_closure requires parentheses.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 221.15: 1506-276 (S) Syntax
error: possible missing '{'?
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 248.3: 1506-273 (E) Missing
type in declaration of ffi_raw_closure.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 251.38: 1506-275 (S)
Unexpected text '*' encountered.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 252.23: 1506-276 (S) Syntax
error: possible missing identifier?
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 251.1: 1506-033 (S)
Function ffi_prep_raw_closure is not valid. Function cannot return a function.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 251.1: 1506-282 (S) The
type of the parameters must be specified in a prototype.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 254.23: 1506-275 (S)
Unexpected text 'void' encountered.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 254.38: 1506-275 (S)
Unexpected text ')' encountered.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 257.43: 1506-275 (S)
Unexpected text '*' encountered.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 258.28: 1506-276 (S) Syntax
error: possible missing identifier?
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 257.1: 1506-033 (S)
Function ffi_prep_java_raw_closure is not valid. Function cannot return a
function.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 257.1: 1506-282 (S) The
type of the parameters must be specified in a prototype.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 260.28: 1506-275 (S)
Unexpected text 'void' encountered.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 260.43: 1506-275 (S)
Unexpected text ')' encountered.
"/sw_install/python-2.5/Modules/_ctypes/ctypes.h", line 71.9: 1506-046 (S)
Syntax error.
"/sw_install/python-2.5/Modules/_ctypes/ctypes.h", line 77.26: 1506-195 (S)
Integral constant expression with a value greater than zero is required.
"/sw_install/python-2.5/Modules/_ctypes/_ctypes.c", line 2804.31: 1506-068 (E)
Operation between types "void*" and "int(*)(void)" is not allowed.
"/sw_install/python-2.5/Modules/_ctypes/_ctypes.c", line 3357.28: 1506-280 (E)
Function argument assignment between types "int(*)(void)" and "void*" is not
allowed.
"/sw_install/python-2.5/Modules/_ctypes/_ctypes.c", line 3417.42: 1506-022 (S)
"pcl" is not a member of "struct {...}".
"/sw_install/python-2.5/Modules/_ctypes/_ctypes.c", line 4749.67: 1506-280 (E)
Function argument assignment between types "void*" and "void*(*)(void*,const
void*,unsigned long)" is not allowed.
"/sw_install/python-2.5/Modules/_ctypes/_ctypes.c", line 4750.66: 1506-280 (E)
Function argument assignment between types "void*" and
"void*(*)(void*,int,unsigned long)" is not allowed.
"/sw_install/python-2.5/Modules/_ctypes/_ctypes.c", line 4751.69: 1506-280 (E)
Function argument assignment between types "void*" and "struct
_object*(*)(const char*,long)" is not allowed.
"/sw_install/python-2.5/Modules/_ctypes/_ctypes.c", line 4752.64: 1506-280 (E)
Function argument assignment between types "void*" and "struct
_object*(*)(void*,struct _object*,struct _object*)" is not allowed.
"/sw_install/python-2.5/Modules/_ctypes/_ctypes.c", line 4754.70: 1506-280 (E)
Function argument assignment between types "void*" and "struct
_object*(*)(const unsigned int*,int)" is not allowed.
building '_ctypes_test' extension
xlc_r -q64 -DNDEBUG -O -I. -I/sw_install/python-2.5/./Include -I./Include -I.
-I/sw_install/python-2.5/Include -I/sw_install/python-2.5 -c
/sw_install/python-2.5/Modules/_ctypes/_ctypes_test.c -o
build/temp.a
[ python-Bugs-1644239 ] Error arrow offset wrong
Bugs item #1644239, was opened at 2007-01-25 09:51 Message generated for change (Comment added) made by gbrandl You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1644239&group_id=5470 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: IDLE Group: Python 2.4 >Status: Closed >Resolution: Invalid Priority: 5 Private: No Submitted By: Cees Timmerman (ctimmerman) Assigned to: Nobody/Anonymous (nobody) Summary: Error arrow offset wrong Initial Comment: >>> def check_path(f): ... asert not '"' in f File "", line 2 asert not '"' in f ^ SyntaxError: invalid syntax It looks like the tab i used to indent was converted to 4 spaces and then each space back to tabs which each got converted to 4 spaces. Python 2.4.4c1 (#2, Oct 11 2006, 21:51:02) [GCC 4.1.2 20060928 (prerelease) (Ubuntu 4.1.1-13ubuntu5)] on linux2 -- >Comment By: Georg Brandl (gbrandl) Date: 2007-01-25 16:30 Message: Logged In: YES user_id=849994 Originator: NO This has nothing to do with tabs, the arrow is at the same position when indenting with spaces. An "asert" alone on a line is not invalid syntax. A line starting with "asert not " is not necessarily invalid too since e.g. "in x" could follow. But as soon as you add "'", it's invalid, so the parsers shows the arrow there. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1644239&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Feature Requests-602345 ] option for not writing .py[co] files
Feature Requests item #602345, was opened at 2002-08-30 11:13 Message generated for change (Comment added) made by gbrandl You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=355470&aid=602345&group_id=5470 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: Python Interpreter Core >Group: None Status: Open Resolution: None Priority: 3 Private: No Submitted By: Matthias Klose (doko) Assigned to: Skip Montanaro (montanaro) Summary: option for not writing .py[co] files Initial Comment: [destilled from http://bugs.debian.org/96111] Currently python tries to write the .py[co] files even in situations, where it will fail, like on read-only mounted file systems. In other situations I don't want python trying to write the compiled files, i.e. having installed the modules as root as part of a distribution, compiled them correctly, there is no need to write them. Or compiling .py files which are configuration files. Is it reasonable to add an option to python (--dont-write-compiled-files) to the interpreter, which doesn't write them? This would not affect existing code at all. -- >Comment By: Georg Brandl (gbrandl) Date: 2007-01-25 16:33 Message: Logged In: YES user_id=849994 Originator: NO Turning in a feature request. -- Comment By: Skip Montanaro (montanaro) Date: 2003-05-22 22:20 Message: Logged In: YES user_id=44345 I have a c.l.py message buried in my python mailbox which raises some Windows-related problems. I have yet to figure that out, but they looked somewhat difficult on first glance. I'll try to dredge that up and attach it to this id. -- Comment By: Neal Norwitz (nnorwitz) Date: 2003-05-22 22:03 Message: Logged In: YES user_id=33168 I think Skip now owns this because of his PEP. :-) -- Comment By: Brett Cannon (bcannon) Date: 2003-05-21 05:50 Message: Logged In: YES user_id=357491 PEP 304 now handles this situation. -- Comment By: Neal Norwitz (nnorwitz) Date: 2003-01-12 21:39 Message: Logged In: YES user_id=33168 You are correct about the patch being incomplete. I still have to do all the doc. I hadn't thought about an env't variable or variable in sys. Both are certainly reasonable. I will update the patch. -- Comment By: Martin v. Löwis (loewis) Date: 2003-01-12 19:47 Message: Logged In: YES user_id=21627 The patch looks good, but is surely incomplete: there should be patches to the documentation, in particular to the man page. It might be also desirable to parallel this option with an environment variable, and/or to expose it writable through the sys module. With the environment variable, people could run Python scripts that won't create .pyc files (as #! /usr/bin/env python does not allow for further command line options). With the API, certain applications could declare that they never want to write .pyc files as they expect to run in parallel with itself, and might cause .pyc conflicts. -- Comment By: Guido van Rossum (gvanrossum) Date: 2002-09-03 15:39 Message: Logged In: YES user_id=6380 I think it's a good idea, but please use a single upper case letter for the option. Python doesn't support long options and I'm not about to start doing so. -- Comment By: Neal Norwitz (nnorwitz) Date: 2002-09-01 23:30 Message: Logged In: YES user_id=33168 Guido, do you think this is a good idea? If so, assign back to me and I'll work up a patch. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=355470&aid=602345&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Feature Requests-602345 ] option for not writing .py[co] files
Feature Requests item #602345, was opened at 2002-08-30 06:13 Message generated for change (Comment added) made by montanaro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=355470&aid=602345&group_id=5470 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Python Interpreter Core Group: None Status: Open Resolution: None Priority: 3 Private: No Submitted By: Matthias Klose (doko) Assigned to: Skip Montanaro (montanaro) Summary: option for not writing .py[co] files Initial Comment: [destilled from http://bugs.debian.org/96111] Currently python tries to write the .py[co] files even in situations, where it will fail, like on read-only mounted file systems. In other situations I don't want python trying to write the compiled files, i.e. having installed the modules as root as part of a distribution, compiled them correctly, there is no need to write them. Or compiling .py files which are configuration files. Is it reasonable to add an option to python (--dont-write-compiled-files) to the interpreter, which doesn't write them? This would not affect existing code at all. -- >Comment By: Skip Montanaro (montanaro) Date: 2007-01-25 10:45 Message: Logged In: YES user_id=44345 Originator: NO Took me awhile (nearly four years!) to find it, but I finally found the c.l.py message I referred to regarding Windows problems. It's attached. Skip File Added: kew-msg -- Comment By: Georg Brandl (gbrandl) Date: 2007-01-25 10:33 Message: Logged In: YES user_id=849994 Originator: NO Turning in a feature request. -- Comment By: Skip Montanaro (montanaro) Date: 2003-05-22 17:20 Message: Logged In: YES user_id=44345 I have a c.l.py message buried in my python mailbox which raises some Windows-related problems. I have yet to figure that out, but they looked somewhat difficult on first glance. I'll try to dredge that up and attach it to this id. -- Comment By: Neal Norwitz (nnorwitz) Date: 2003-05-22 17:03 Message: Logged In: YES user_id=33168 I think Skip now owns this because of his PEP. :-) -- Comment By: Brett Cannon (bcannon) Date: 2003-05-21 00:50 Message: Logged In: YES user_id=357491 PEP 304 now handles this situation. -- Comment By: Neal Norwitz (nnorwitz) Date: 2003-01-12 15:39 Message: Logged In: YES user_id=33168 You are correct about the patch being incomplete. I still have to do all the doc. I hadn't thought about an env't variable or variable in sys. Both are certainly reasonable. I will update the patch. -- Comment By: Martin v. Löwis (loewis) Date: 2003-01-12 13:47 Message: Logged In: YES user_id=21627 The patch looks good, but is surely incomplete: there should be patches to the documentation, in particular to the man page. It might be also desirable to parallel this option with an environment variable, and/or to expose it writable through the sys module. With the environment variable, people could run Python scripts that won't create .pyc files (as #! /usr/bin/env python does not allow for further command line options). With the API, certain applications could declare that they never want to write .pyc files as they expect to run in parallel with itself, and might cause .pyc conflicts. -- Comment By: Guido van Rossum (gvanrossum) Date: 2002-09-03 10:39 Message: Logged In: YES user_id=6380 I think it's a good idea, but please use a single upper case letter for the option. Python doesn't support long options and I'm not about to start doing so. -- Comment By: Neal Norwitz (nnorwitz) Date: 2002-09-01 18:30 Message: Logged In: YES user_id=33168 Guido, do you think this is a good idea? If so, assign back to me and I'll work up a patch. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=355470&aid=602345&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1643943 ] strptime %U broken
Bugs item #1643943, was opened at 2007-01-24 15:00
Message generated for change (Comment added) made by bcannon
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1643943&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Library
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Brian Nahas (bnahas)
>Assigned to: Brett Cannon (bcannon)
Summary: strptime %U broken
Initial Comment:
Python 2.4.1 (#1, May 16 2005, 15:19:29)
[GCC 4.0.0 20050512 (Red Hat 4.0.0-5)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from time import strptime
>>> strptime('2006-53-0', '%Y-%U-%w')
(2006, 12, 31, 0, 0, 0, 6, 365, -1)
>>> strptime('2007-00-0', '%Y-%U-%w')
(2006, 12, 24, 0, 0, 0, 6, -7, -1)
>>> strptime('2007-01-0', '%Y-%U-%w')
(2007, 1, 7, 0, 0, 0, 6, 7, -1)
>>> strptime('2007-02-0', '%Y-%U-%w')
(2007, 1, 7, 0, 0, 0, 6, 7, -1)
>>> strptime('2007-03-0', '%Y-%U-%w')
(2007, 1, 14, 0, 0, 0, 6, 14, -1)
>>>
Note that in the above test, Sunday of week 1 and week 2 for 2007 reported the
date as 2007-01-07 and Sunday of week 0 was reported as 2006-12-24, not
2006-12-31. I'm not sure exactly what is correct, but the inconsistencies are
bothersome.
Same results on:
Python 2.4.4c1 (#70, Oct 11 2006, 10:59:14) [MSC v.1310 32 bit (Intel)] on win32
--
>Comment By: Brett Cannon (bcannon)
Date: 2007-01-25 10:50
Message:
Logged In: YES
user_id=357491
Originator: NO
I will try to fix this when I can. Just to warn you, Brian, I really
doubt I will put the effort into backporting this to 2.4.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1643943&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1643943 ] strptime %U broken
Bugs item #1643943, was opened at 2007-01-24 23:00
Message generated for change (Comment added) made by bnahas
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1643943&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Library
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Brian Nahas (bnahas)
Assigned to: Brett Cannon (bcannon)
Summary: strptime %U broken
Initial Comment:
Python 2.4.1 (#1, May 16 2005, 15:19:29)
[GCC 4.0.0 20050512 (Red Hat 4.0.0-5)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from time import strptime
>>> strptime('2006-53-0', '%Y-%U-%w')
(2006, 12, 31, 0, 0, 0, 6, 365, -1)
>>> strptime('2007-00-0', '%Y-%U-%w')
(2006, 12, 24, 0, 0, 0, 6, -7, -1)
>>> strptime('2007-01-0', '%Y-%U-%w')
(2007, 1, 7, 0, 0, 0, 6, 7, -1)
>>> strptime('2007-02-0', '%Y-%U-%w')
(2007, 1, 7, 0, 0, 0, 6, 7, -1)
>>> strptime('2007-03-0', '%Y-%U-%w')
(2007, 1, 14, 0, 0, 0, 6, 14, -1)
>>>
Note that in the above test, Sunday of week 1 and week 2 for 2007 reported the
date as 2007-01-07 and Sunday of week 0 was reported as 2006-12-24, not
2006-12-31. I'm not sure exactly what is correct, but the inconsistencies are
bothersome.
Same results on:
Python 2.4.4c1 (#70, Oct 11 2006, 10:59:14) [MSC v.1310 32 bit (Intel)] on win32
--
>Comment By: Brian Nahas (bnahas)
Date: 2007-01-25 19:39
Message:
Logged In: YES
user_id=562121
Originator: YES
No worries.
Here's what I'm doing as a work-around. I needed to convert the results
of a mysql YEARWEEK field to the sunday at the start of that week:
import datetime
def mysqlWeekToSundayDate(yearweek):
year = int(yearweek[0:4])
week = int(yearweek[4:6])
day = datetime.date(year, 1, 1)
dayDelta = datetime.timedelta(1)
weekDelta = datetime.timedelta(7)
while day.strftime("%w") != "0":
day = day + dayDelta
day = day + ((week - 1) * weekDelta)
return day
I'm relatively new to Python so it is probably not the most efficient
method but it does the job.
--
Comment By: Brett Cannon (bcannon)
Date: 2007-01-25 18:50
Message:
Logged In: YES
user_id=357491
Originator: NO
I will try to fix this when I can. Just to warn you, Brian, I really
doubt I will put the effort into backporting this to 2.4.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1643943&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1637120 ] Python 2.5 fails to build on AIX 5.3 (xlc_r compiler)
Bugs item #1637120, was opened at 2007-01-16 22:06
Message generated for change (Comment added) made by loewis
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1637120&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Build
Group: Python 2.5
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Orlando Irrazabal (oirraza)
Assigned to: Thomas Heller (theller)
Summary: Python 2.5 fails to build on AIX 5.3 (xlc_r compiler)
Initial Comment:
Initial Comment:
Build of Python 2.5 on AIX 5.3 with xlc_r fails with the below error message.
The configure line is:
./configure --with-gcc="xlc_r -q64" --with-cxx="xlC_r -q64" --disable-ipv6
AR="ar -X64"
[...]
building '_ctypes' extension
xlc_r -q64 -DNDEBUG -O -I. -I/sw_install/python-2.5/./Include
-Ibuild/temp.aix-5.3-2.5/libffi/include -Ibuild/temp.aix-5.3-2.5/libffi
-I/sw_install/python-2.5/Modules/_ctypes/libffi/src -I./Include -I.
-I/sw_install/python-2.5/Include -I/sw_install/python-2.5 -c
/sw_install/python-2.5/Modules/_ctypes/_ctypes.c -o
build/temp.aix-5.3-2.5/sw_install/python-2.5/Modules/_ctypes/_ctypes.o
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 221.3: 1506-166 (S)
Definition of function ffi_closure requires parentheses.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 221.15: 1506-276 (S) Syntax
error: possible missing '{'?
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 248.3: 1506-273 (E) Missing
type in declaration of ffi_raw_closure.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 251.38: 1506-275 (S)
Unexpected text '*' encountered.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 252.23: 1506-276 (S) Syntax
error: possible missing identifier?
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 251.1: 1506-033 (S)
Function ffi_prep_raw_closure is not valid. Function cannot return a function.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 251.1: 1506-282 (S) The
type of the parameters must be specified in a prototype.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 254.23: 1506-275 (S)
Unexpected text 'void' encountered.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 254.38: 1506-275 (S)
Unexpected text ')' encountered.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 257.43: 1506-275 (S)
Unexpected text '*' encountered.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 258.28: 1506-276 (S) Syntax
error: possible missing identifier?
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 257.1: 1506-033 (S)
Function ffi_prep_java_raw_closure is not valid. Function cannot return a
function.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 257.1: 1506-282 (S) The
type of the parameters must be specified in a prototype.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 260.28: 1506-275 (S)
Unexpected text 'void' encountered.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 260.43: 1506-275 (S)
Unexpected text ')' encountered.
"/sw_install/python-2.5/Modules/_ctypes/ctypes.h", line 71.9: 1506-046 (S)
Syntax error.
"/sw_install/python-2.5/Modules/_ctypes/ctypes.h", line 77.26: 1506-195 (S)
Integral constant expression with a value greater than zero is required.
"/sw_install/python-2.5/Modules/_ctypes/_ctypes.c", line 2804.31: 1506-068 (E)
Operation between types "void*" and "int(*)(void)" is not allowed.
"/sw_install/python-2.5/Modules/_ctypes/_ctypes.c", line 3357.28: 1506-280 (E)
Function argument assignment between types "int(*)(void)" and "void*" is not
allowed.
"/sw_install/python-2.5/Modules/_ctypes/_ctypes.c", line 3417.42: 1506-022 (S)
"pcl" is not a member of "struct {...}".
"/sw_install/python-2.5/Modules/_ctypes/_ctypes.c", line 4749.67: 1506-280 (E)
Function argument assignment between types "void*" and "void*(*)(void*,const
void*,unsigned long)" is not allowed.
"/sw_install/python-2.5/Modules/_ctypes/_ctypes.c", line 4750.66: 1506-280 (E)
Function argument assignment between types "void*" and
"void*(*)(void*,int,unsigned long)" is not allowed.
"/sw_install/python-2.5/Modules/_ctypes/_ctypes.c", line 4751.69: 1506-280 (E)
Function argument assignment between types "void*" and "struct
_object*(*)(const char*,long)" is not allowed.
"/sw_install/python-2.5/Modules/_ctypes/_ctypes.c", line 4752.64: 1506-280 (E)
Function argument assignment between types "void*" and "struct
_object*(*)(void*,struct _object*,struct _object*)" is not allowed.
"/sw_install/python-2.5/Modules/_ctypes/_ctypes.c", line 4754.70: 1506-280 (E)
Function argument assignment between types "void*" and "struct
_object*(*)(const unsigned int*,int)" is not allowed.
building '_ctypes_test' extension
xlc_r -q64 -DNDEBUG -O -I. -I/sw_install/python-2.5/./Include -I./Include -I.
-I/sw_install/python-2.5/Include -I/sw_install/python-2.5 -c
/sw_install/python-2.5/Modules/_ctypes/_ctypes_test.c -o
build/temp.ai
[ python-Bugs-1643943 ] strptime %U broken
Bugs item #1643943, was opened at 2007-01-24 15:00
Message generated for change (Comment added) made by bcannon
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1643943&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Library
Group: Python 2.4
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Brian Nahas (bnahas)
Assigned to: Brett Cannon (bcannon)
Summary: strptime %U broken
Initial Comment:
Python 2.4.1 (#1, May 16 2005, 15:19:29)
[GCC 4.0.0 20050512 (Red Hat 4.0.0-5)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from time import strptime
>>> strptime('2006-53-0', '%Y-%U-%w')
(2006, 12, 31, 0, 0, 0, 6, 365, -1)
>>> strptime('2007-00-0', '%Y-%U-%w')
(2006, 12, 24, 0, 0, 0, 6, -7, -1)
>>> strptime('2007-01-0', '%Y-%U-%w')
(2007, 1, 7, 0, 0, 0, 6, 7, -1)
>>> strptime('2007-02-0', '%Y-%U-%w')
(2007, 1, 7, 0, 0, 0, 6, 7, -1)
>>> strptime('2007-03-0', '%Y-%U-%w')
(2007, 1, 14, 0, 0, 0, 6, 14, -1)
>>>
Note that in the above test, Sunday of week 1 and week 2 for 2007 reported the
date as 2007-01-07 and Sunday of week 0 was reported as 2006-12-24, not
2006-12-31. I'm not sure exactly what is correct, but the inconsistencies are
bothersome.
Same results on:
Python 2.4.4c1 (#70, Oct 11 2006, 10:59:14) [MSC v.1310 32 bit (Intel)] on win32
--
>Comment By: Brett Cannon (bcannon)
Date: 2007-01-25 13:33
Message:
Logged In: YES
user_id=357491
Originator: NO
Rev. 53564 (trunk) has the fix and 2.5 will as soon as a commit problem I
am having is fixed. I basically rewrote the algorithm to have a generic
calculation for the Julian day and just shifted the length of week 0 and
the day of the week based on whether %U or %W was specified. Cut out all
the other edge cases which were messy and confusing.
--
Comment By: Brian Nahas (bnahas)
Date: 2007-01-25 11:39
Message:
Logged In: YES
user_id=562121
Originator: YES
No worries.
Here's what I'm doing as a work-around. I needed to convert the results
of a mysql YEARWEEK field to the sunday at the start of that week:
import datetime
def mysqlWeekToSundayDate(yearweek):
year = int(yearweek[0:4])
week = int(yearweek[4:6])
day = datetime.date(year, 1, 1)
dayDelta = datetime.timedelta(1)
weekDelta = datetime.timedelta(7)
while day.strftime("%w") != "0":
day = day + dayDelta
day = day + ((week - 1) * weekDelta)
return day
I'm relatively new to Python so it is probably not the most efficient
method but it does the job.
--
Comment By: Brett Cannon (bcannon)
Date: 2007-01-25 10:50
Message:
Logged In: YES
user_id=357491
Originator: NO
I will try to fix this when I can. Just to warn you, Brian, I really
doubt I will put the effort into backporting this to 2.4.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1643943&group_id=5470
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1637120 ] Python 2.5 fails to build on AIX 5.3 (xlc_r compiler)
Bugs item #1637120, was opened at 2007-01-16 18:06
Message generated for change (Comment added) made by oirraza
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1637120&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Build
Group: Python 2.5
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Orlando Irrazabal (oirraza)
Assigned to: Thomas Heller (theller)
Summary: Python 2.5 fails to build on AIX 5.3 (xlc_r compiler)
Initial Comment:
Initial Comment:
Build of Python 2.5 on AIX 5.3 with xlc_r fails with the below error message.
The configure line is:
./configure --with-gcc="xlc_r -q64" --with-cxx="xlC_r -q64" --disable-ipv6
AR="ar -X64"
[...]
building '_ctypes' extension
xlc_r -q64 -DNDEBUG -O -I. -I/sw_install/python-2.5/./Include
-Ibuild/temp.aix-5.3-2.5/libffi/include -Ibuild/temp.aix-5.3-2.5/libffi
-I/sw_install/python-2.5/Modules/_ctypes/libffi/src -I./Include -I.
-I/sw_install/python-2.5/Include -I/sw_install/python-2.5 -c
/sw_install/python-2.5/Modules/_ctypes/_ctypes.c -o
build/temp.aix-5.3-2.5/sw_install/python-2.5/Modules/_ctypes/_ctypes.o
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 221.3: 1506-166 (S)
Definition of function ffi_closure requires parentheses.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 221.15: 1506-276 (S) Syntax
error: possible missing '{'?
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 248.3: 1506-273 (E) Missing
type in declaration of ffi_raw_closure.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 251.38: 1506-275 (S)
Unexpected text '*' encountered.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 252.23: 1506-276 (S) Syntax
error: possible missing identifier?
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 251.1: 1506-033 (S)
Function ffi_prep_raw_closure is not valid. Function cannot return a function.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 251.1: 1506-282 (S) The
type of the parameters must be specified in a prototype.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 254.23: 1506-275 (S)
Unexpected text 'void' encountered.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 254.38: 1506-275 (S)
Unexpected text ')' encountered.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 257.43: 1506-275 (S)
Unexpected text '*' encountered.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 258.28: 1506-276 (S) Syntax
error: possible missing identifier?
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 257.1: 1506-033 (S)
Function ffi_prep_java_raw_closure is not valid. Function cannot return a
function.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 257.1: 1506-282 (S) The
type of the parameters must be specified in a prototype.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 260.28: 1506-275 (S)
Unexpected text 'void' encountered.
"build/temp.aix-5.3-2.5/libffi/include/ffi.h", line 260.43: 1506-275 (S)
Unexpected text ')' encountered.
"/sw_install/python-2.5/Modules/_ctypes/ctypes.h", line 71.9: 1506-046 (S)
Syntax error.
"/sw_install/python-2.5/Modules/_ctypes/ctypes.h", line 77.26: 1506-195 (S)
Integral constant expression with a value greater than zero is required.
"/sw_install/python-2.5/Modules/_ctypes/_ctypes.c", line 2804.31: 1506-068 (E)
Operation between types "void*" and "int(*)(void)" is not allowed.
"/sw_install/python-2.5/Modules/_ctypes/_ctypes.c", line 3357.28: 1506-280 (E)
Function argument assignment between types "int(*)(void)" and "void*" is not
allowed.
"/sw_install/python-2.5/Modules/_ctypes/_ctypes.c", line 3417.42: 1506-022 (S)
"pcl" is not a member of "struct {...}".
"/sw_install/python-2.5/Modules/_ctypes/_ctypes.c", line 4749.67: 1506-280 (E)
Function argument assignment between types "void*" and "void*(*)(void*,const
void*,unsigned long)" is not allowed.
"/sw_install/python-2.5/Modules/_ctypes/_ctypes.c", line 4750.66: 1506-280 (E)
Function argument assignment between types "void*" and
"void*(*)(void*,int,unsigned long)" is not allowed.
"/sw_install/python-2.5/Modules/_ctypes/_ctypes.c", line 4751.69: 1506-280 (E)
Function argument assignment between types "void*" and "struct
_object*(*)(const char*,long)" is not allowed.
"/sw_install/python-2.5/Modules/_ctypes/_ctypes.c", line 4752.64: 1506-280 (E)
Function argument assignment between types "void*" and "struct
_object*(*)(void*,struct _object*,struct _object*)" is not allowed.
"/sw_install/python-2.5/Modules/_ctypes/_ctypes.c", line 4754.70: 1506-280 (E)
Function argument assignment between types "void*" and "struct
_object*(*)(const unsigned int*,int)" is not allowed.
building '_ctypes_test' extension
xlc_r -q64 -DNDEBUG -O -I. -I/sw_install/python-2.5/./Include -I./Include -I.
-I/sw_install/python-2.5/Include -I/sw_install/python-2.5 -c
/sw_install/python-2.5/Modules/_ctypes/_ctypes_test.c -o
build/temp.a
[ python-Bugs-1644987 ] ./configure --prefix=/ breaks, won't build C modules
Bugs item #1644987, was opened at 2007-01-25 21:34 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1644987&group_id=5470 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Build Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jim Shankland (jas11c) Assigned to: Nobody/Anonymous (nobody) Summary: ./configure --prefix=/ breaks, won't build C modules Initial Comment: This appears to be a new issue with Python 2.5 Building Python 2.5 on Fedora Core 5: ./configure --prefix=/ --enable-shared make fails to build the C modules, as a "-L." is missing from the gcc command line used to generate the module.so file from the module.o file. Using any other value for --prefix works. Setting the environment variable LDFLAGS to "-L." before running ./configure appears to be a successful workaround. Here is a representative failure (all the C modules fail). Note the "cannot find -lpython2.5" message; this is because -L. is missing frmo the gcc command line. building 'crypt' extension gcc -pthread -fPIC -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -I. -I/local/home/jas/Software/Languages/Python/Python-2.5/./Include -I./Include -I. -I/usr/local/include -I/local/home/jas/Software/Languages/Python/Python-2.5/Include -I/local/home/jas/Software/Languages/Python/Python-2.5 -c /local/home/jas/Software/Languages/Python/Python-2.5/Modules/cryptmodule.c -o build/temp.linux-i686-2.5/local/home/jas/Software/Languages/Python/Python-2.5/Modules/cryptmodule.o gcc -pthread -shared build/temp.linux-i686-2.5/local/home/jas/Software/Languages/Python/Python-2.5/Modules/cryptmodule.o -L//lib -L/usr/local/lib -L/lib/python2.5/config -lcrypt -lpython2.5 -o build/lib.linux-i686-2.5/crypt.so /usr/bin/ld: cannot find -lpython2.5 collect2: ld returned 1 exit status -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1644987&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
