New submission from Remi Pointel :
Hi,
"make clean" failed on OpenBSD with this error:
find: -exec: no terminating ";"
*** Error code 1 (ignored)
It seems that "-exec" with "+" is a GNU extension.
Are you OK with this diff which does the same and is m
Remi Pointel added the comment:
FYI I tested with Python 3.3, but I didn't look for 2.7 and 3.2, I think
modifications are also needed.
--
___
Python tracker
<http://bugs.python.org/is
Remi Pointel added the comment:
> According to the man page, find -print0 and xargs -r are also GNU extensions.
> Even though they work on OpenBSD (do they?), they could still break on some
> platforms.
Yes, it works fine, but you're allright.
> As find -exec cmd {} '
Remi Pointel added the comment:
Please see this:
http://bugs.python.org/issue8665
http://hg.python.org/cpython/rev/5468f3aee4ae/
--
___
Python tracker
<http://bugs.python.org/issue13
Remi Pointel added the comment:
> How about using the -depth option then? It's in POSIX but does OpenBSD have
> it? The man page of GNU find says it has a -d option (that does the same as
> -depth) for compatibility with BSD.
Yes, we have this option:
-depth This primary alway
New submission from Remi Pointel :
Hello,
I was running test_datetime.py and it failed on OpenBSD.
I have tested with Python 2.7, Python 3.2 and Python 3.3.
Python 2.7:
test_datetime.py: ok
test_srtftime.py: failed (see attached file: test_strftime_python27.log)
Have a lot of:
Conflict for
Changes by Remi Pointel :
Added file: http://bugs.python.org/file23706/test_datetime_python33.log
___
Python tracker
<http://bugs.python.org/issue13414>
___
___
Python-bug
Changes by Remi Pointel :
Added file: http://bugs.python.org/file23707/test_strftime_python27.log
___
Python tracker
<http://bugs.python.org/issue13414>
___
___
Python-bug
Changes by Remi Pointel :
Added file: http://bugs.python.org/file23708/test_strftime_python32.log
___
Python tracker
<http://bugs.python.org/issue13414>
___
___
Python-bug
Changes by Remi Pointel :
Added file: http://bugs.python.org/file23709/test_strftime_python33.log
___
Python tracker
<http://bugs.python.org/issue13414>
___
___
Python-bug
Remi Pointel added the comment:
Sure.
--
Added file: http://bugs.python.org/file23710/strftime.c
___
Python tracker
<http://bugs.python.org/issue13414>
___
___
Remi Pointel added the comment:
Thanks Antoine for your response.
Python 3.2.1 and Python 2.4.6 have been successfully installed (but Python
2.5.4 and Python 2.7.1 failed).
--
___
Python tracker
<http://bugs.python.org/issue7
Remi Pointel added the comment:
Hi,
this is the patch in OpenBSD.
Source:
http://www.openbsd.org/cgi-bin/cvsweb/ports/lang/python/2.7/patches/patch-Modules_selectmodule_c
Could be usefull to work together and advance on this problem.
Thanks a lot.
Remi.
--
Added file: http
Remi Pointel added the comment:
Hi,
I have tested on OpenBSD -current, and it seems to work fine:
$ ./python -E -bb Lib/test/test_mmap.py
test_access_parameter (__main__.MmapTests) ... ok
test_anonymous (__main__.MmapTests) ... ok
test_bad_file_desc (__main__.MmapTests) ... ok
Remi Pointel added the comment:
Hi,
what information do you need to advance on this bug?
Cheers,
Remi.
--
___
Python tracker
<http://bugs.python.org/issue12
New submission from Remi Pointel :
Hello,
test_fcntl failed on OpenBSD 5.0.
It's ok when we add openbsd5 in the tuple of sys.platform (patch attached).
Thanks a lot,
Remi.
--
files: patch-Lib_test_test_fcntl_py
messages: 142784
nosy: rpointel
priority: normal
severity: normal
s
Remi Pointel added the comment:
Thanks a lot, I prefer to use sys.platform.startswith too.
Remi.
--
___
Python tracker
<http://bugs.python.org/issue12
New submission from Remi Pointel :
Hello,
I try to build Python 3.3 on OpenBSD, and it failed to build these modules:
_socket (so _ssl too).
Errors are:
/home/remi/dev/cpython_test/Modules/socketmodule.c: In function 'sock_recvmsg':
/home/remi/dev/cpython_test/Modules/socketmod
Changes by Remi Pointel :
Added file:
http://bugs.python.org/file23016/socketmodule_build_error_openbsd.log
___
Python tracker
<http://bugs.python.org/issue12
New submission from Remi Pointel :
Hello,
/usr/tmp is not (used) on OpenBSD.
We have specific patch to do this, but I prefer to have this modification
upstream.
2.5:
http://www.openbsd.org/cgi-bin/cvsweb/ports/lang/python/2.5/patches/patch-Lib_tempfile_py
2.7:
http://www.openbsd.org/cgi
Remi Pointel added the comment:
I was reporting this because I thought it was better to include this upstream.
However, I understand if you don't want to include this specific case.
We can keep this patch in our tree, I understand your pos
Remi Pointel added the comment:
> I could be missing something, but why do you have this patch in the first
> place?
I'm recently working on porting Python for OpenBSD, and this patch exists since
python2.5 (since 4 years in our tree). So I don't have all responses, but I
Remi Pointel added the comment:
Hi,
I think this issue is relied to issue 12181.
I have made tests.
1)with no patch:
testPair (__main__.TestKQueue) ... ok
test_create_event (__main__.TestKQueue) ... FAIL
test_create_queue (__main__.TestKQueue) ... ok
New submission from Remi Pointel :
Hi,
During the regress tests on OpenBSD, test_posix.test_fdlistdir() segfault.
Details:
$ ./python ./Tools/scripts/run_tests.py test_posix
/home/remi/dev/cpython_test/python -W default -bb -E -m test -r -w -j 0 -u
all,-largefile,-network,-urlfetch,-audio
Remi Pointel added the comment:
Hi,
thanks for your response.
Yes it always segfault:
$ ./python -c 'import os; print(os.fdlistdir(os.open("/tmp", os.O_RDONLY)))'
zsh: segmentation fault (core dumped) ./python -c 'import os;
print(os.fdlistdir(os.open("/tmp&qu
Remi Pointel added the comment:
Hi,
I tested with this program in C:
#include
#include
#include
#include
int
main(void)
{
DIR *d;
struct dirent *dp;
int dfd;
if ((d = fdopendir((dfd = open("/tmp", O_RDONLY == NULL) {
fprintf(stderr, "C
Remi Pointel added the comment:
Hi,
this is the result of gcc -E on Modules/posixmodule.o, asked by haypo.
Thanks for your help,
Cheers,
Remi.
--
Added file: http://bugs.python.org/file23072/gcc-E-Modules_posixmodule_output
___
Python tracker
New submission from Remi Pointel :
Hello,
the test_stack_overflow failed on OpenBSD.
Don't hesitate if you need more information.
Details:
$ ./python Lib/test/test_faulthandler.py
test_disable (__main__.FaultHandlerTests) ... ok
test_dump_traceback (__main__.FaultHandlerTests) .
Remi Pointel added the comment:
Info: I read issue 12469 but I prefered to create new issue.
--
___
Python tracker
<http://bugs.python.org/issue12868>
___
___
Remi Pointel added the comment:
Hi,
results:
>Out of curiosity, could you try this:
>$ ./python -c "import faulthandler; faulthandler.enable();
>faulthandler._stack_overflow()"; echo $?
$ ./python -c "import faulthandler; faulthandler.enable();
faulthandler._stack_
Remi Pointel added the comment:
> Yeah, it's a recent regression: I opened the issue #12871. I don't think that
> it's specific to OpenBSD.
Thanks.
--
___
Python tracker
<http://bu
Remi Pointel added the comment:
Hi,
without-threads, it segfault:
$ ./python -c "import faulthandler; faulthandler.enable();
faulthandler._stack_overflow()"; echo $?
Fatal Python error: Segmentation fault
Current thread 0x:
File "", line 1 in
zsh: segm
Remi Pointel added the comment:
However, if I run test_faulthandler.py, it seems to be ok:
$ ./python Lib/test/test_faulthandler.py
test_disable (__main__.FaultHandlerTests) ... ok
test_dump_traceback (__main__.FaultHandlerTests) ... ok
test_dump_traceback_file (__main__.FaultHandlerTests
Remi Pointel added the comment:
> Rémi : what happens if you manually add
> extern DIR *fdopendir(int fd);
> at the beginning of posixmodule.c?
Hello,
it seems to correctly work:
./python Lib/test/test_posix.py
testNoArgFunctions (__main__.PosixTester) ... ok
test_access
Remi Pointel added the comment:
> It would be nice if you could find out in which header file fdopendir() is
> defined.
Hi,
fdopendir() is in /usr/include/dirent.h:
#if __POSIX_VISIBLE >= 200809
DIR *fdopendir(int);
#endif
You could find the file dirent.h here:
http://www.openbs
Remi Pointel added the comment:
Hi,
it seems to solve the problem (tested on OpenBSD 4.9 and OpenBSD-current).
* test_posix.py on OpenBSD 4.9:
[...]
Ran 79 tests in 0.508s
OK (skipped=35)
* test_posix.py on OpenBSD-current:
it continues to segfault, but I have opened an other ticket for this
New submission from Remi Pointel :
Hi,
these tests block on OpenBSD:
-test_interrupted_write_unbuffered()
-test_interrupted_write_buffered()
-test_interrupted_write_text()
-test_interrupterd_read_retry_buffered()
-test_interrupterd_read_retry_text()
-test_interrupterd_write_retry_buffered
New submission from Remi Pointel :
Hi,
I have few problems in test_socket.py.
1) test_sendall_interrupted blocks on OpenBSD, I must Ctrl+c to interrupt the
test. I added a skip to have full regress tests, but I think it's not the
proper way.
I have run it into gdb, and ctrl
Remi Pointel added the comment:
I add bt output with gdb 7, to have more informations.
--
Added file: http://bugs.python.org/file23105/OpenBSD_test_socket_gdb.log
___
Python tracker
<http://bugs.python.org/issue12
Remi Pointel added the comment:
> What happens if you run a code equivalent to test_sendall_interrupted on its
> own? I mean, if you try something like this:
Hi, it blocks too:
$ gdb -args ./python
[...]
(gdb) run
Starting program: /usr/ports/pobj/Python-3.2.2/Python-3.2.2/python
Remi Pointel added the comment:
> @rpointel: Does the fix work for you? If yes, I will close the issue.
Hi, yes it sounds good for me:
$ hg pull -u
$ ./configure && make
$ ./python Lib/test/test_posix.py
[...]
test_fdlistdir (__main__.PosixTester) ... ok
[...]
Ran 79 tests i
Remi Pointel added the comment:
I think we could close this bug because it's du to the pthread library on
OpenBSD and not Python.
We are switching to rthreads and I can't reproduce this bug.
Thanks for your help and sorry for
Remi Pointel added the comment:
I think we could close this bug because it's du to the pthread library on
OpenBSD and not Python.
We are switching to rthreads and I can't reproduce this bug.
Thanks for your help and sorry for
Changes by Remi Pointel :
--
nosy: +rpointel
___
Python tracker
<http://bugs.python.org/issue21082>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Remi Pointel :
--
nosy: +rpointel
___
Python tracker
<http://bugs.python.org/issue21356>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Remi Pointel:
Hi,
I tested the regress tests on a machine which does not have the ssl module, and
I have 2 errors in Lib/test/test_urllib2net.py. I think it should skip the test
instead.
Attached is a diff I wrote, it's based on Lib/test/test_poplib.py.
Don't h
Remi Pointel added the comment:
Are you ok with this diff reworked?
--
Added file: http://bugs.python.org/file35505/Lib_test_test_urllib2net_py.diff
___
Python tracker
<http://bugs.python.org/issue21
Remi Pointel added the comment:
For your information, this bug has been fixed in OpenBSD and the developper has
contacted the NetBSD developper:
http://marc.info/?l=openbsd-tech&m=140209064821540&w=2
So I think we could close this issue because it's a system issu
New submission from Remi Pointel:
When I run the regress tests on OpenBSD 5.4-current, the test test_inspect.py
failed because the module _multiprocessing is not available, instead of
skipping the test:
FAILED (errors=1)
Traceback (most recent call last):
File "./Lib/test/test_inspe
Remi Pointel added the comment:
Yes, but it needs an import to use test.support.multiprocessing.
--
___
Python tracker
<http://bugs.python.org/issue19134>
___
___
Remi Pointel added the comment:
Thanks :)
--
___
Python tracker
<http://bugs.python.org/issue19134>
___
___
Python-bugs-list mailing list
Unsubscribe:
Remi Pointel added the comment:
Hi,
sorry to reopen this bug but it seams that your commit was not ok:
test_qualname_source (__main__.TestMain) ... ERROR
==
ERROR: test_qualname_source (__main__.TestMain
Remi Pointel added the comment:
It's ok now, thanks:
test_qualname_source (__main__.TestMain) ... skipped 'multiprocessing required
to test __qualname__ for source files'
--
___
Python tracker
<http://bugs.pyt
Changes by Remi Pointel :
--
nosy: +rpointel
___
Python tracker
<http://bugs.python.org/issue19884>
___
___
Python-bugs-list mailing list
Unsubscribe:
Remi Pointel added the comment:
I close this bug because it's corrected by the commit (revision 1.2):
http://www.openbsd.org/cgi-bin/cvsweb/src/lib/libc/time/wcsftime.c
It was a bug in our wcsftime.
Thanks.
--
resolution: -> invalid
status: open -
New submission from Remi Pointel:
Hi,
I have 2 tests which "failed" on OpenBSD (tested on i386, amd64 and sparc64) in:
- test_threadsignals.py/test_lock_acquire_interruption
- test_threadsignals.py/test_rlock_acquire_in
Remi Pointel added the comment:
arf, sorry for the noise... I didn't seen this.
--
___
Python tracker
<http://bugs.python.org/issue20564>
___
___
Pytho
Remi Pointel added the comment:
I'm in -current (5.5-beta).
--
___
Python tracker
<http://bugs.python.org/issue20564>
___
___
Python-bugs-list mailing list
Remi Pointel added the comment:
Thanks for your response.
> When running the test, is faulthandler enabled (--timeout option)?
It seems yes:
#
$ PYTHONPATH=. ./python Tools/scripts/run_tests.py -
Remi Pointel added the comment:
> Can you please test interrupt_lock_acquire.py? It should be the same than the
> unit test, but in a fresh Python process.
Thanks for your response, this is what I have:
$ PYTHONPATH=. ./python ./interrupt_lock_acquire.py
Traceback (most recent cal
Remi Pointel added the comment:
Hi,
I think you forgot to attach the diff.
Python 3.3 is in OpenBSD since 5.4.
--
___
Python tracker
<http://bugs.python.org/issue20
Remi Pointel added the comment:
> You may report the feature request to OpenBSD kernel if you want. Until
> OpenBSD implements it, the test is now skipped in Python.
Yes, it's done yet.
However, it's good to skip it until
Remi Pointel added the comment:
Hello,
I have exactly the same problem with Python 2.7.13 on OpenBSD.
Works fine with the same patch.
Remi.
--
nosy: +rpointel
versions: +Python 2.7
___
Python tracker
<http://bugs.python.org/issue28
New submission from Remi Pointel:
Hi,
I'm trying to build Python on OpenBSD-current, but it does not build because it
seems that PY_GETENTROPY does not have a value.
$ make
...
gcc -pthread -c -fno-strict-aliasing -Wsign-compare -Wunreachable-code -DNDEBUG
-g -fwrapv -O3 -Wall -Ws
New submission from Remi Pointel:
Hi,
the test test_getsetlocale_issue1813 in ./Lib/test/test_locale.py failed on
OpenBSD:
==
...sss..testing with ('tr_TR', 'ISO8859-9&
Remi Pointel added the comment:
Hi,
maybe we should add the LIBRESSL_ information available in opensslv.h (as it
has be done for OpenSSL):
$ grep LIBRESSL /usr/include/ssl/opensslv.h
#define LIBRESSL_VERSION_NUMBER 0x2003L
#define LIBRESSL_VERSION_TEXT "LibreSSL 2.3.0&quo
Remi Pointel added the comment:
Maybe we could check if the functionality is available instead of checking a
version? What do you think about that?
--
___
Python tracker
<http://bugs.python.org/issue23
Remi Pointel added the comment:
With this patch it works fine on OpenBSD with LibreSSL.
Could you test on a Linux machine with OpenSSL supporting ALPN please?
Thanks spil@ for the idea.
--
keywords: +patch
Added file: http://bugs.python.org/file40556/python_have_alpn.diff
Remi Pointel added the comment:
I would prefer to keep this script with the version referring to the version of
python used (pyvenv-3.4, pyvenv-3.5, ...).
--
nosy: +rpointel
___
Python tracker
<http://bugs.python.org/issue25
Remi Pointel added the comment:
Good, I think we should test on a machine with a version of openssl that does
not support ALPN to be sure.
--
___
Python tracker
<http://bugs.python.org/issue23
Remi Pointel added the comment:
Attached is the diff to use defined(PY_GETENTROPY) instead of #define
PY_GETENTROPY 1.
--
Added file: http://bugs.python.org/file40631/Python_random_c
___
Python tracker
<http://bugs.python.org/issue25
Changes by Remi Pointel :
--
nosy: rpointel
priority: normal
severity: normal
status: open
title: json
___
Python tracker
<http://bugs.python.org/issue25
Remi Pointel added the comment:
Sorry I clicked on "create" before adding info in comment.
When I run the test_json suite on OpenBSD, I have a segfault:
$ egdb ./python
GNU gdb (GDB) 7.10
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version
Changes by Remi Pointel :
--
title: json -> test_json segfault on OpenBSD
___
Python tracker
<http://bugs.python.org/issue25342>
___
___
Python-bugs-list mai
Remi Pointel added the comment:
It fails on test_endless_recursion:
$ LD_LIBRARY_PATH=. PYTHONPATH=./Lib/ ./python ./Lib/test/test_json -v
test_endless_recursion (test.test_json.test_recursion.TestPyRecursion) ... zsh:
segmentation fault (core dumped
Remi Pointel added the comment:
It's good when I entered "ulimit -s 8192". Sorry for the noise...
--
___
Python tracker
<http://bugs.pyt
76 matches
Mail list logo
