Henry Precheur added the comment:
The patch works well with on amd64/OpenBSD-current (CVS from May 14 or
15).
I don't have access to a 4.7-stable right now.
On Fri, May 14, 2010 at 05:58:10PM +, Stefan Krah wrote:
>
> Stefan Krah added the comment:
>
> Mark, thanks. -
Henry Precheur added the comment:
The bug is also present with Python 3.1 on OpenBSD 4.7-current.
--
___
Python tracker
<http://bugs.python.org/issue8
Changes by Henry Precheur :
--
versions: +Python 3.1
___
Python tracker
<http://bugs.python.org/issue8714>
___
___
Python-bugs-list mailing list
Unsubscribe:
Henry Precheur <[EMAIL PROTECTED]> added the comment:
According to config.log the readline functions are correctly detected. I
tested the patch with Python 2.5 & 2.6 and both work with the test I
posted on issue 3645.
___
Python tracker <[EM
New submission from Henry Precheur <[EMAIL PROTECTED]>:
Compiling `multiprocessing` on OpenBSD fails. `iovec` is not declared.
Adding the following line to multiprocessing.c solves the problem:
#include
But right after I got:
./python:build/lib.openbsd-4.4-amd64-2.6/_multiprocess
New submission from Henry Precheur <[EMAIL PROTECTED]>:
test_fileio
test test_fileio failed -- Traceback (most recent call last):
File "/home/henry/compile/python2.6/Lib/test/test_fileio.py", line
155, in testAbles
self.assertEquals(f.seekable(), False)
AssertionErro
Henry Precheur <[EMAIL PROTECTED]> added the comment:
The patch bsd2.diff seems to work. There was a little typo in it (a
missing @). (correction attached)
Added file: http://bugs.python.org/file11547/bsd3.diff
___
Python tracker <[EMAIL PROTECTE
Changes by Henry Precheur <[EMAIL PROTECTED]>:
--
versions: +Python 2.5
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3920>
___
__
Henry Precheur <[EMAIL PROTECTED]> added the comment:
I just tested the patch and it fixes the problem.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Henry Precheur <[EMAIL PROTECTED]> added the comment:
This problem was probably solved in issue #1204.
--
nosy: +henry.precheur
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.o
New submission from Henry Precheur <[EMAIL PROTECTED]>:
$ python2.5
Python 2.5.2 (r252:60911, Jun 16 2008, 15:20:47)
[GCC 3.3.5 (propolice)] on op
Henry Precheur <[EMAIL PROTECTED]> added the comment:
Looks like this patch should also be applied to python 2.6 & 3.
I did not tested but the patch is trivial enough to be applied without
too much fear of breaking something ;)
___
Python track
New submission from Henry Precheur <[EMAIL PROTECTED]>:
I tried to compile Python 3000 under OpenBSD and the compilation fails
because of a 'MemoryError':
Fatal Python error: can't create sys.path
object : MemoryError()
type: MemoryError
refcount: 4
address : 0x20ab
Henry Precheur <[EMAIL PROTECTED]> added the comment:
I forgot to mention, I made to following modification to configure.in so
I could compile Python 3000 on OpenBSD 4.4
--- configure.in(revision 66037)
+++ configure.in(working copy)
@@ -250,7 +250,7 @@
# On OpenBSD, se
Henry Precheur <[EMAIL PROTECTED]> added the comment:
Indeed it looks like it is the source of the problem.
I created a patch to fix it.
But it looks like there is another problem, instead of crashing the
Python interpreter goes into interactive mode instead of executing the
'setup
Henry Precheur <[EMAIL PROTECTED]> added the comment:
Looks like my other issue is unrelated. It is caused by a buggy mbstowcs.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
New submission from Henry Precheur <[EMAIL PROTECTED]>:
The function mbstowcs is buggy on OpenBSD <= 4.4:
http://www.openbsd.org/cgi-bin/cvsweb/src/lib/libc/locale/multibyte_sb.c#rev1.7
Because of this the following command fails:
./python -E setup.py build
The attached patch fixes th
Henry Precheur <[EMAIL PROTECTED]> added the comment:
I removed my previous patch. It was not dealing with all broken mbstowcs
cases and yours is much better.
Some comments on the other patch:
I don't think the macro HAVE_BROKEN_MBSTOWCS alone is a perfect idea. It
won't fix th
Changes by Henry Precheur <[EMAIL PROTECTED]>:
Removed file: http://bugs.python.org/file11266/fix_mbstowcs_openbsd.diff
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Henry Precheur <[EMAIL PROTECTED]> added the comment:
I am now able to finish the build and the interpreter seems to be
working. So it is all good :)
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Henry Precheur <[EMAIL PROTECTED]> added the comment:
I just compiled the latest version of trunk. The problem seems to be
fixed. And according to config.log & nm, readline.so is linked with the
right function.
___
Python tracker <[EMAIL PROT
Henry Precheur <[EMAIL PROTECTED]> added the comment:
Here is a better patch which use the workaround only if wcschr is broken.
I was able to build the python interpreter and to run regrtest.py with
it (some tests fail but it is very likely to be bugs in the modules)
Added file
Henry Precheur added the comment:
I found some bsddb code left in setup.py. Patch attached.
--
nosy: +henry.precheur
Added file: http://bugs.python.org/file14434/setup.py.remove-bsddb.diff
___
Python tracker
<http://bugs.python.org/issue2
Henry Precheur added the comment:
I tested the patch with py3k on OpenBSD 4.6 beta and it worked.
But I must admit I don't fully understand what the patch does ...
--
nosy: +henry.precheur
___
Python tracker
<http://bugs.python.org/i
New submission from Henry Precheur :
A kqueue's test doesn't pass on OpenBSD 4.6-beta, 4.4, & 4.5:
FAILED (failures=1)
Traceback (most recent call last):
File "Lib/test/test_kqueue.py", line 186, in
test_main()
File "Lib/test/test_kqueu
New submission from Henry Precheur :
On OpenBSD the file /usr/include/rpcsvc/ypclnt.h contains the following
declaration:
struct ypall_callback {
/* return non-0 to stop getting called */
int (*foreach)(unsigned long, char *, int, char *, int, void *);
char *data
Changes by Henry Precheur :
--
components: +Tests
___
Python tracker
<http://bugs.python.org/issue6419>
___
___
Python-bugs-list mailing list
Unsubscribe:
Henry Precheur added the comment:
FreeBSD does.
http://svn.freebsd.org/viewvc/base/stable/7/include/rpcsvc/ypclnt.h?revision=172506&view=markup
But NetBSD doesn't:
http://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/src/include/rpcsvc/ypclnt.h?rev=1.13&content-type=text/plain&o
Henry Precheur added the comment:
It works on OpenBSD, but I don't have any FreeBSD to test. I should be
safe to commit though, the patch is rather trivial.
--
___
Python tracker
<http://bugs.python.org/i
New submission from Henry Precheur :
"make test" calls Python with the -E option which ignore the PYTHON*
environment variables, but Python sub-processes aren't necessarily called with
the -E options. For example test_displayhook_unencodable in test_cmd_line. This
created probl
New submission from Henry Precheur :
The function find_executable crashes if PATH is not defined.
I admit that it's an extreme case, but it's probably better to on the safe side
of things.
What about using the current directory only if PATH is not defined? This seems
to be a
Henry Precheur added the comment:
Here's a small patch to call regression tests without any environment variable
defined. It's probably a good thing to run all the tests with a clean state,
this way they are less likely to fail for mysterious external reasons. Fo
New submission from Henry Precheur :
Parser/asdl_c.py uses `/usr/bin/env python' as an interpreter. But Python
executable is not always `python'. With OpenBSD's ports, CPython's interpreters
are installed as pythonX.Y. There's a variable PYTHON in the Makefile, th
Henry Precheur added the comment:
Indeed, I didn't realize that PYTHON was the name of the target interpreter and
not the name a an already installed interpreter.
--
___
Python tracker
<http://bugs.python.org/is
Henry Precheur added the comment:
Sorry "crash" wasn't the right term. It's just that distutils tests fail.
I ran into that when trying to run unit tests without any environment
variable (see #12401).
$ env -i ./python ./Lib/test/regrtest.py test_distutils
[1/1]
Henry Precheur added the comment:
I don't know exactly in which context find_executable should be used,
but after taking a closer look it seems that returning None when PATH is
not defined could "work".
--
___
Python tracker
<http
Henry Precheur added the comment:
I think that returning None would be a better option. The function
documentation says:
Tries to find 'executable' in the directories listed in 'path'.
A string listing directories separated by 'os.pathsep'; defaults to
os
Changes by Henry Precheur :
--
title: distutils crashes if PATH is not defined -> distutils tests fail if PATH
is not defined
___
Python tracker
<http://bugs.python.org/issu
Henry Precheur added the comment:
OK it makes sense.
I'm working on fixing the tests. I'm not done yet, but I've attached a patch
with my work in progress (some tests still fail). Do you have any comments?
I'll post a complete version later today or tomorrow.
---
Changes by Henry Precheur :
Removed file: http://bugs.python.org/file22501/fix_distutils_test.diff
___
Python tracker
<http://bugs.python.org/issue12420>
___
___
Pytho
Henry Precheur added the comment:
I've fixed the last failing tests, but I'm unsure it's the right way to do it.
Take a look at the part for Lib/distutils/tests/test_build_ext.py. I just check
that os.environ['PATH'] is defined. I'm not 100% certain that this
41 matches
Mail list logo
