[issue21392] Python on Cygwin: subprocess.call BlockingIOError: [Errno 11] Resource temporarily unavailable

2014-05-05 Thread dellair jie

dellair jie added the comment:

Eric,

Very much appreciated for your offer to help.
This issue is with Cygwin fork(), documented here:
http://cygwin.com/faq.html#faq.using.fixing-fork-failures

I am closing the issue.
Have a great day!

--
resolution:  - not a bug
status: open - closed

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21392
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue21124] _struct module compilation error under Cygwin 1.7.17 on Python 3.4

2014-04-30 Thread dellair jie

dellair jie added the comment:

Fixed with the patch.

--
resolution:  - fixed
status: open - closed

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21124
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue21392] Python on Cygwin: subprocess.call BlockingIOError: [Errno 11] Resource temporarily unavailable

2014-04-30 Thread dellair jie

New submission from dellair jie:

Folks,

I am running Python 3.4 on Cygwin 1.7.17 on Windows 2008.
The constant error I get is:

Traceback (most recent call last):
  File M:/sb3_ljie/bce/cmTools/lib/CC.py, line 321, in standAlone
results = Process.execute (cmd = cmd, opts = opts)
  File M:/sb3_ljie/bce/cmTools/lib/Process.py, line 327, in execute
timeout = timeout)
  File /usr/local/lib/python3.4/subprocess.py, line 535, in call
with Popen(*popenargs, **kwargs) as p:
  File /usr/local/lib/python3.4/subprocess.py, line 848, in __init__
restore_signals, start_new_session)
  File /usr/local/lib/python3.4/subprocess.py, line 1379, in _execute_child
restore_signals, start_new_session, preexec_fn)
BlockingIOError: [Errno 11] Resource temporarily unavailable

Python script is invoked via socket (server runs Cygwin inetd).

While the script (snippet) Process.py is as below with relatively large data 
return:
import subprocess, os, tempfile, re
def execute (cmd = None,
 opts = None,
 log = None,
 verify = False,
 cmdlog = False,
 audit = False,
 logappend = False,
 ignorestatus = False,
 umask = None,
 host = None,
 interrupt = None,
 timeout = None,
 forceaudit = False):
global __signal
global __signalList
returnData = {status: 0, rawstatus: 0, interrupt: 0,
  stdout: None, stderr: None}
os.environ[ENV] = 

stdOutHandle, stdOut = tempfile.mkstemp (text = True)
stdErrHandle, stdErr = tempfile.mkstemp (text = True)

if re.match (\s, cmd): cmd = ' + cmd + '
cmd = [cmd]
opts = opts.split()
cmd.extend (opts)

if not verify:
if umask: originalUmask = os.umask (umask)

if interrupt:
for idex, item in enumerate (__signalList):
if item: signal.signal (idex, interrupt)

__signal = 0

returnData[rawstatus] = subprocess.call (cmd, stdout = stdOutHandle,
   stderr = stdErrHandle,
   timeout = timeout)
returns = returnData[rawstatus]
os.close (stdOutHandle)
os.close (stdErrHandle)

Br,
Dellair

--
messages: 217585
nosy: dellair.jie
priority: normal
severity: normal
status: open
title: Python on Cygwin: subprocess.call BlockingIOError: [Errno 11] Resource 
temporarily unavailable
versions: Python 3.4

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21392
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue21392] Python on Cygwin: subprocess.call BlockingIOError: [Errno 11] Resource temporarily unavailable

2014-04-30 Thread dellair jie

Changes by dellair jie dell...@gmail.com:


--
components: +IO
type:  - resource usage

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21392
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue21392] Python on Cygwin: subprocess.call BlockingIOError: [Errno 11] Resource temporarily unavailable

2014-04-30 Thread dellair jie

dellair jie added the comment:

The value of __signal and __signalList:
__signal=0
__signalList=[None] * 256
__signalList[signal.SIGHUP] = signalHandler
__signalList[signal.SIGQUIT] = signalHandler
__signalList[signal.SIGUSR1] = signalHandler
__signalList[signal.SIGUSR2] = signalHandler

signal.signal (signal.SIGHUP,  signalHandler)
signal.signal (signal.SIGQUIT, signalHandler)
signal.signal (signal.SIGUSR2, signalHandler)
signal.signal (signal.SIGUSR1, signalHandler)

I think those are irrelevant though.

cmd is a command and that is working.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21392
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue21124] _struct module compilation error under Cygwin 1.7.17 on Python 3.4

2014-04-29 Thread dellair jie

dellair jie added the comment:

Hello masamoto,

The patch you provided works quite well.
The build passed and Python calls are successfully.
Please let me know what else you need me to test in order to have the patch 
accepted or else feel free to close it with Resolution Fixed.

Thanks,
Dellair

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21124
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue21085] compile error Python3.3 on Cygwin

2014-04-29 Thread dellair jie

dellair jie added the comment:

Finally got it compiled on Cygwin! :)

Victor,

I am still having issue with the make test on Cygwin, hence can only do some 
manual testing:

Output:
 info = signal.sigwaitinfo({signal.SIGINT})
^C

 info = signal.struct_siginfo((2, 128, 0, 0, 0, 3))
Traceback (most recent call last):
  File stdin, line 1, in module
TypeError: signal.struct_siginfo() takes an at least 7-sequence (6-sequence 
given)
 info = signal.struct_siginfo((2, 128, 0, 0, 0, 3, 0))
Traceback (most recent call last):
  File stdin, line 1, in module
TypeError: signal.struct_siginfo() takes an at most 6-sequence (7-sequence 
given)
 help(signal.struct_siginfo)
 |  --
 |  Data descriptors defined here:
 |
 |  si_code
 |  signal code
 |
 |  si_errno
 |  errno associated with this signal
 |
 |  si_pid
 |  sending process ID
 |
 |  si_signo
 |  signal number
 |
 |  si_status
 |  exit value or signal
 |
 |  si_uid
 |  real user ID of sending process
 |
 |  --

Feel free to let me know if more testing is required.

Br,
Dellair

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21085
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue21124] _struct module compilation error under Cygwin 1.7.17 on Python 3.4

2014-04-02 Thread dellair jie

dellair jie added the comment:

Neil,

It doesn't look like a duplicate of Issue6672.
The one in Issue6672 was for Mingw, all the patches simply added __MINGW32__ to 
__CYGWIN__ build structure.
While my issue is, the build failed with _struct.c on Cygwin. So the module is 
recognized, just didn't pass the compilation.

Br,
Dellair

--
status: pending - open

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21124
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue21124] _struct module compilation error under Cygwin 1.7.17 on Python 3.4

2014-04-02 Thread dellair jie

dellair jie added the comment:

Yamamoto,

Thanks, the patch you offered did make the _struct error disappeared. I will do 
a bit more testing.

Dellair

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21124
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue21085] compile error Python3.3 on Cygwin

2014-04-01 Thread dellair jie

dellair jie added the comment:

Martin,

Here is the values presented on Python 3.4.0, in fact they are the same as 
3.3.2, please note the key difference.
/* #undef HAVE_SIGTIMEDWAIT */
#define HAVE_SIGWAIT 1
#define HAVE_SIGWAITINFO 1
The SIGTIMEDWAIT is undef while the SIGWAIT is defined.
The patch Victor found 
(https://github.com/Alexpux/MSYS2-packages/blob/master/python3/3.3.2-cygwin-siginfo.patch)
 to modify sigalmodule.c works on both 3.3.2 and 3.4 (at least the build went 
through the sign failure.) 
So shall we close this issue?

Petrov,
Thanks a loot!
The patch you offered about parser works with 3.3.2 and 3.4. 
There is further issues with the build on Cygwin and I will raise it in a 
separate issue.

Br,
Dellair

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21085
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue21085] compile error Python3.3 on Cygwin

2014-04-01 Thread dellair jie

dellair jie added the comment:

Victor,

Would you please be more specific on test_signal?

Br,
Dellair

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21085
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue21085] compile error Python3.3 on Cygwin

2014-04-01 Thread dellair jie

dellair jie added the comment:

Victor,

I suppose that Python needs to be built successfully before running test_signal.
Three patches were applied in Python 3.4.0. However, the build failed to build 
_struct module.

Should I open another Issue to track it?

As long as the build goes through completely on Cygwin, I will go back and do 
the signal test.

Br,
Dellair

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21085
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue21123] Compilation error on _struct module on Python 3.4

2014-04-01 Thread dellair jie

New submission from dellair jie:

Dear all,

I am compiling Python 3.4 on Cygwin 1.7.17.

The following has been done in order to reach the point where _struct module 
failed.
 A clean Python 3.4
 Applied patches:
  cygwin_si_band.patch in Issue21085
  0001-CYGWIN-issue13756-Python-make-fail-on-cygwin.patch in issue13756
  0019-MINGW-export-_PyNode_SizeOf-as-PyAPI-for-parser-modu.patch in issue186373
 configure + make

The issue happened during make:
building '_struct' extension
gcc -Wno-unused-result -Werror=declaration-after-statement -DNDEBUG -g -fwrapv 
-O3 -Wall -Wstrict-prototypes -I./Include -I. -IInclude 
-I/cygdrive/c/temp/Python-3.4.0/Include -I/cygdrive/c/temp/Python-3.4.0 -c 
/cygdrive/c/temp/Python-3.4.0/Modules/_struct.c -o 
build/temp.cygwin-1.7.17-i686-3.4/cygdrive/c/temp/Python-3.4.0/Modules/_struct.o
/cygdrive/c/temp/Python-3.4.0/Modules/_struct.c:1630:5: error: initializer 
element is not constant
/cygdrive/c/temp/Python-3.4.0/Modules/_struct.c:1630:5: error: (near 
initialization for ‘unpackiter_type.ob_base.ob_base.ob_type’)

Please feel free to find the build.log and the output of _struct.c.txt (gcc 
with -dD -E -DPy_BUILD_core) for more information.

Thanks in advance,
Br,
Dellair

--
files: _struct.c.txt
messages: 215320
nosy: dellair.jie
priority: normal
severity: normal
status: open
title: Compilation error on _struct module on Python 3.4
versions: Python 3.4
Added file: http://bugs.python.org/file34694/_struct.c.txt

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21123
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue21124] Compilation error on _struct module on Python 3.4

2014-04-01 Thread dellair jie

New submission from dellair jie:

Dear all,

I am compiling Python 3.4 on Cygwin 1.7.17.

The following has been done in order to reach the point where _struct module 
failed.
 A clean Python 3.4
 Applied patches:
  cygwin_si_band.patch in Issue21085
  0001-CYGWIN-issue13756-Python-make-fail-on-cygwin.patch in issue13756
  0019-MINGW-export-_PyNode_SizeOf-as-PyAPI-for-parser-modu.patch in issue186373
 configure + make

The issue happened during make:
building '_struct' extension
gcc -Wno-unused-result -Werror=declaration-after-statement -DNDEBUG -g -fwrapv 
-O3 -Wall -Wstrict-prototypes -I./Include -I. -IInclude 
-I/cygdrive/c/temp/Python-3.4.0/Include -I/cygdrive/c/temp/Python-3.4.0 -c 
/cygdrive/c/temp/Python-3.4.0/Modules/_struct.c -o 
build/temp.cygwin-1.7.17-i686-3.4/cygdrive/c/temp/Python-3.4.0/Modules/_struct.o
/cygdrive/c/temp/Python-3.4.0/Modules/_struct.c:1630:5: error: initializer 
element is not constant
/cygdrive/c/temp/Python-3.4.0/Modules/_struct.c:1630:5: error: (near 
initialization for ‘unpackiter_type.ob_base.ob_base.ob_type’)

Please feel free to find the build.log and the output of _struct.c.txt (gcc 
with -dD -E -DPy_BUILD_core) for more information.

Thanks in advance,
Br,
Dellair

--
files: _struct.c.txt
messages: 215321
nosy: dellair.jie
priority: normal
severity: normal
status: open
title: Compilation error on _struct module on Python 3.4
versions: Python 3.4
Added file: http://bugs.python.org/file34695/_struct.c.txt

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21124
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue21124] Compilation error on _struct module on Python 3.4

2014-04-01 Thread dellair jie

dellair jie added the comment:

The full build log

--
Added file: http://bugs.python.org/file34696/Build.log

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21124
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue21123] Compilation error on _struct module on Python 3.4

2014-04-01 Thread dellair jie

dellair jie added the comment:

Duplicated with Issue21124

--
resolution:  - duplicate
status: open - closed

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21123
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue21085] compile error Python3.3 on Cygwin

2014-03-31 Thread dellair jie

dellair jie added the comment:

Yes, my pleasure. 

After configure on Cygwin, there is pyconfig.h generated, variables are as 
following:
/* #undef HAVE_SIGTIMEDWAIT */
/* #define HAVE_SIGWAITINFO 1 */

The error disappeared once changed HAVE_SIGWAITINFO to undef.
However, it encountered another issue mentioned here:
http://bugs.python.org/issue13756

The patches provided seem only for 3.2.2, not sure if it is ok to apply them 
directly on 3.3.2?

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21085
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue21085] compile error Python3.3 on Cygwin

2014-03-31 Thread dellair jie

dellair jie added the comment:

Applied the patch 0001-CYGWIN-issue13756-Python-make-fail-on-cygwin.patch in 
case: http://bugs.python.org/issue13756

The build failed with parser module:
building 'parser' extension
gcc -Wno-unused-result -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes 
-I./Include -I. -IInclude -I/cygdrive/c/temp/Python-3.3.2/Include 
-I/cygdrive/c/temp/Python-3.3.2 -c 
/cygdrive/c/temp/Python-3.3.2/Modules/parsermodule.c -o 
build/temp.cygwin-1.7.17-i686-3.3/cygdrive/c/temp/Python-3.3.2/Modules/parsermodule.o
gcc -shared -Wl,--enable-auto-image-base 
build/temp.cygwin-1.7.17-i686-3.3/cygdrive/c/temp/Python-3.3.2/Modules/parsermodule.o
 -L. -L/usr/local/lib -lpython3.3m -o 
build/lib.cygwin-1.7.17-i686-3.3/parser.dll
build/temp.cygwin-1.7.17-i686-3.3/cygdrive/c/temp/Python-3.3.2/Modules/parsermodule.o:
 In function `parser_sizeof':
/cygdrive/c/temp/Python-3.3.2/Modules/parsermodule.c:371: undefined reference 
to `__PyNode_SizeOf'
collect2: ld returned 1 exit status

Could anyone shed some lights please?

Br,
Li

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21085
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue21085] compile error Python3.3 on Cygwin

2014-03-31 Thread dellair jie

dellair jie added the comment:

Martin,

Certainly running on 3.4 now.
The output of the command is attached.

Will try to look into it tomorrow if no immediate follow up post.

Br,
Li

--
Added file: http://bugs.python.org/file34682/signalmodule.output.txt

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21085
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue21085] compile error Python3.3 on Cygwin

2014-03-31 Thread dellair jie

dellair jie added the comment:

Martin,

Thanks for the analysis!

The following values came from Python 3.3.2, the #define HAVE_SIGWAITINFO 1 was 
without comment sign, I commented it out for the build to go through.
/* #undef HAVE_SIGTIMEDWAIT */
/* #define HAVE_SIGWAITINFO 1 */

The output was from 3.4, haven't checked the values yet, might be different. 
Will check it tomorrow.

Br,
Dellair

--
versions: +Python 3.4

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21085
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue21085] compile error Python3.3 on Cygwin

2014-03-28 Thread dellair jie

New submission from dellair jie:

Folks,

Is Cygwin supported by Python? We met the following error when compiling Python 
3.3.2 on Cygwin 1.7.17:

gcc -c -Wno-unused-result -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes 
-I. -IInclude -I./Include-DPy_BUILD_CORE -o Modules/main.o Modules/main.c
Modules/main.c:17:0: warning: PATH_MAX redefined
/usr/include/limits.h:336:0: note: this is the location of the previous 
definition
Modules/main.c: In function ‘Py_Main’:
Modules/main.c:561:5: warning: implicit declaration of function ‘_setmode’
gcc -c -Wno-unused-result -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes 
-I. -IInclude -I./Include-DPy_BUILD_CORE -o Modules/gcmodule.o 
Modules/gcmodule.c
gcc -Wno-unused-result -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes 
-I. -IInclude -I./Include-DPy_BUILD_CORE  -c ./Modules/_threadmodule.c -o 
Modules/_threadmodule.o
gcc -Wno-unused-result -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes 
-I. -IInclude -I./Include-DPy_BUILD_CORE  -c ./Modules/signalmodule.c -o 
Modules/signalmodule.o
./Modules/signalmodule.c: In function ‘fill_siginfo’:
./Modules/signalmodule.c:745:5: error: ‘siginfo_t’ has no member named ‘si_band’
Makefile:1501: recipe for target `Modules/signalmodule.o' failed
make: *** [Modules/signalmodule.o] Error 1

Any lights would be appreciated.

Thanks,

--
components: Build
messages: 215050
nosy: dellair.jie
priority: normal
severity: normal
status: open
title: compile error Python3.3 on Cygwin
versions: Python 3.3

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21085
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue20163] ValueError: time data does not match format

2014-03-28 Thread dellair jie

dellair jie added the comment:

We've found a workaround to handle the timestr manually.
Thanks,

--
status: open - closed

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20163
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue21085] compile error Python3.3 on Cygwin

2014-03-28 Thread dellair jie

dellair jie added the comment:

Victor,

I did do ./configure, without any parameters. Should I use it with 
--without-signal-module option? Will all signals be disabled if this option 
is specified?

From Python document, it mentions Windows support the following signals:
signal.SIGINT, signal.SIGTERM, signal.SIGABRT, signal.SIGFPE, signal.SIGILL, 
signal.SIGSEGV
 
The following are found in pyconfig.h.in

 804 /* Define to 1 if you have the `sigtimedwait' function. */
 805 #undef HAVE_SIGTIMEDWAIT
 810 /* Define to 1 if you have the `sigwaitinfo' function. */
 811 #undef HAVE_SIGWAITINFO


Br,
Li

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21085
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue20163] ValueError: time data does not match format

2014-01-07 Thread dellair jie

New submission from dellair jie:

Hello,

We are using Python 3.3.2 for HPUX11.31.

The following error happens only on HPUX, works on SunOS, RHEL, AIX.

python
Python 3.3.2 (default, Dec  9 2013, 14:04:25) [C] on hp-ux11
Type help, copyright, credits or license for more information.
 from datetime import datetime
 datetime.strptime (10-Dec-13.20:07:49, %d-%b-%y.%H:%M:%S)
Traceback (most recent call last):
  File stdin, line 1, in module
  File /python/lib/python3.3/_strptime.py, line 500, in _strptime_datetime
tt, fraction = _strptime(data_string, format)
  File /python/lib/python3.3/_strptime.py, line 337, in _strptime
(data_string, format))
ValueError: time data '10-Dec-13.20:07:49' does not match format 
'%d-%b-%y.%H:%M:%S'

It looks like a bug. Could you please shed some lights?

Thanks in advance,

Br,
Li

--
components: Library (Lib)
messages: 207542
nosy: dellair.jie
priority: normal
severity: normal
status: open
title: ValueError: time data does not match format
type: behavior
versions: Python 3.3

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20163
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue20163] ValueError: time data does not match format

2014-01-07 Thread dellair jie

dellair jie added the comment:

Victor,

Thanks for the comment.

Isolated, the error happens at:

 import time
 time.strptime (Dec, %b)
Traceback (most recent call last):
  File stdin, line 1, in module
  File /python/lib/python3.3/_strptime.py, line 494, in _strptime_time
tt = _strptime(data_string, format)[0]
  File /python/lib/python3.3/_strptime.py, line 340, in _strptime
data_string[found.end():])
ValueError: unconverted data remains: Dec

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20163
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue20163] ValueError: time data does not match format

2014-01-07 Thread dellair jie

dellair jie added the comment:

The output of command:

$ date +'%b'
Jan
$ uname -a
HP-UX test5 B.11.31 U ia64 4201936010 unlimited-user license

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20163
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue20163] ValueError: time data does not match format

2014-01-07 Thread dellair jie

dellair jie added the comment:

We get an empty string for the name. :)

 time.strftime(%b, time.gmtime(1387036705))
''

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20163
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue20163] ValueError: time data does not match format

2014-01-07 Thread dellair jie

dellair jie added the comment:

Victor,

HPUX 11.31 was first released in 2007, we keep upgrading and the latest update 
is in 2013. ^_^

A workaround sounds fine. By re-implementing strftime(), do you mean to patch 
it from: http://bugs.python.org/issue1777412?

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20163
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue19661] AIX: Python: RuntimeError invalid slot offset when importing a module in _ssl module

2013-12-10 Thread dellair jie

dellair jie added the comment:

Folks,

I am closing this bug as it seems to be fixed with a with a redownload of 
original package.

Thanks for sharing the ideas.

Br,
Li

--
resolution:  - fixed
status: open - closed

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19661
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue19661] AIX: Python: RuntimeError invalid slot offset when importing a module in _ssl module

2013-11-27 Thread dellair jie

dellair jie added the comment:

I have rebuilt Python 3.3.2 with GCC 4.4.0 on AIX6.1.
There was no warning. But, still seeing the same import offset runtime error:

gcc -pthread -DNDEBUG -g -fwrapv -O0 -Wall -Wstrict-prototypes -IInclude -I. 
-Iopenssl/include -Iopenssl/include -IPython/Python-3.3.2-aix/Include 
-IPython/Python-3.3.2-aix -c Python/Python-3.3.2-aix/Modules/_ssl.c -o 
build/temp.aix-6.1-3.3Python/Python-3.3.2-aix/Modules/_ssl.o

Python/Python-3.3.2-aix/Modules/ld_so_aix gcc -pthread 
-bI:Python/Python-3.3.2-aix/Modules/python.exp 
build/temp.aix-6.1-3.3Python/Python-3.3.2-aix/Modules/_ssl.o -Lopenssl/lib 
-Lopenssl/lib -lssl -lcrypto -o build/lib.aix-6.1-3.3/_ssl.so

*** WARNING: importing extension _ssl failed with 
build/lib.aix-6.1-3.3/_ssl.so: class 'RuntimeError': invalid slot offset: 
traceback object at 0x30378788

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19661
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue19661] AIX: Python: RuntimeError invalid slot offset when importing a module in _ssl module

2013-11-24 Thread dellair jie

dellair jie added the comment:

It would be appreciated if someone could shed some lights on how to rebuild a 
single module (ssl) from source code package and import it to python. 

Thanks in advance!

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19661
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue19661] AIX: Python: RuntimeError invalid slot offset when importing a module in _ssl module

2013-11-22 Thread dellair jie

dellair jie added the comment:

Folks,

Is there a patch to apply on this, I tried to search online, found one similar 
post but was solved until the poster switched to another version of xlc. Do we 
need to use another compiler(I will have to build though)?

Please don't hesitate to contact me if further information is needed for 
analysis.

Thanks,

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19661
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue19661] AIX: Python: RuntimeError invalid slot offset when importing a module in _ssl module

2013-11-21 Thread dellair jie

dellair jie added the comment:

Still seeing the same error without optimization, the build log from HPUX 
11.31IA is also attached for reference (maybe irrelevance though ^^):

AIX 6.1:
cc -qlanglvl=extc89 -O0 -IInclude -I. -I/usr/local/include -c 
/aix/Modules/_ssl.c -o build/temp.aix-6.1-3.3-pydebug/aix/Modules/_ssl.o
/aix/Modules/_ssl.c, line 262.17: 1506-196 (W) Initialization between types 
void* and struct _object*(*)(struct {...}*) is not allowed.
/aix/Modules/ld_so_aix cc -qlanglvl=extc89 -bI:/aix/Modules/python.exp 
build/temp.aix-6.1-3.3-pydebug/aix/Modules/_ssl.o -L/usr/local/lib -lssl 
-lcrypto -o build/lib.aix-6.1-3.3-pydebug/_ssl.so
ld: 0711-224 WARNING: Duplicate symbol: .bcopy
ld: 0711-224 WARNING: Duplicate symbol: .memcpy
ld: 0711-224 WARNING: Duplicate symbol: .memmove
ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more information.
*** WARNING: importing extension _ssl failed with 
build/lib.aix-6.1-3.3-pydebug/_ssl.so: class 'RuntimeError': invalid slot 
offset: traceback object at 0x30366038

HPUX11.31:
building '_ssl' extension
cc +z -O0 -IInclude -I. -I/hpux/Include -I/hpux -c /hpux/Modules/_ssl.c -o 
build/temp.hp-ux-B.11.31-ia64-3.3-pydebug/hpux/Modules/_ssl.o
/hpux/Modules/_ssl.c, line 383: warning #4232-D:
  conversion from PyObject * to a more strictly aligned type
  PySocketSockObject * may cause misaligned access
= (PySocketSockObject *) PyWeakref_GetObject(obj-Socket);
  ^

/hpux/Modules/_ssl.c, line 499: warning #4232-D:
  conversion from PyObject * to a more strictly aligned type
  PySocketSockObject * may cause misaligned access
= (PySocketSockObject *) PyWeakref_GetObject(self-Socket);
  ^

/hpux/Modules/_ssl.c, line 1220: warning #2111-D:
  statement is unreachable
  if (!_PyIsSelectable_fd(s-sock_fd))
  ^

/hpux/Modules/_ssl.c, line 1253: warning #4232-D:
  conversion from PyObject * to a more strictly aligned type
  PySocketSockObject * may cause misaligned access
= (PySocketSockObject *) PyWeakref_GetObject(self-Socket);
  ^

/hpux/Modules/_ssl.c, line 1363: warning #4232-D:
  conversion from PyObject * to a more strictly aligned type
  PySocketSockObject * may cause misaligned access
= (PySocketSockObject *) PyWeakref_GetObject(self-Socket);
  ^

/hpux/Modules/_ssl.c, line 1484: warning #4232-D:
  conversion from PyObject * to a more strictly aligned type
  PySocketSockObject * may cause misaligned access
= (PySocketSockObject *) PyWeakref_GetObject(self-Socket);
  ^

ld -b build/temp.hp-ux-B.11.31-ia64-3.3-pydebug/hpux/Modules/_ssl.o 
-L/usr/local/lib -lssl -lcrypto -o 
build/lib.hp-ux-B.11.31-ia64-3.3-pydebug/_ssl.so
*** WARNING: importing extension _ssl failed with class 'RuntimeError': 
invalid slot offset

Please let me know if further information is required.

Br,

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19661
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue19661] Python: RuntimeError: invalid slot offset when importing a module

2013-11-20 Thread dellair jie

New submission from dellair jie:

Dear all,

I am getting above error when trying to import ssl module. In fact, the error 
showed up during the build and _ssl module was added to the failed module list. 
However, the compilation and link went well. 

There was no error on compilation and link phases, only some warnings. However, 
during Python build, there is an import phase right after the link, which shows 
the same error as stated.
building '_ssl' extension 
xlc_r -DNDEBUG -O -IInclude -I. -I/usr/local/include -c /aix/Modules/_ssl.c -o 
build/temp.aix-6.1-3.3/aix/Modules/_ssl.o
 /aix/Modules/_ssl.c, line 262.17: 1506-196 (W) Initialization between types 
void* and struct _object*(*)(struct {...}*) is not allowed.
 /aix/Modules/ld_so_aix xlc_r -bI:/aix/Modules/python.exp 
build/temp.aix-6.1-3.3/aix/Modules/_ssl.o -L/usr/local/lib -lssl -lcrypto -o 
build/lib.aix-6.1-3.3/_ssl.so
 ld: 0711-224 WARNING: Duplicate symbol: .bcopy 
ld: 0711-224 WARNING: Duplicate symbol: .memcpy 
ld: 0711-224 WARNING: Duplicate symbol: .memmove 
ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more information. 
*** WARNING: importing extension _ssl failed with 
build/lib.aix-6.1-3.3/_ssl.so: class 'RuntimeError': invalid slot offset: 
traceback object at 0x3017e9e0

I went through google to search for similar issue/solution however no succeeds. 
Hence I suppose it is a bug.

Env: Python: 3.3.2 
OpenSSL: 0.9.8y (also tried 0.9.7) 
OS: AIX 6.1 (also tried on HPUX_1131_IA, same problem)

--
components: Build
messages: 203465
nosy: dellair.jie
priority: normal
severity: normal
status: open
title: Python: RuntimeError: invalid slot offset when importing a module
type: compile error
versions: Python 3.3

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19661
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com