[issue4639] Build failure on OpenBSD 4.4-current regarding lstat()

2008-12-12 Thread Edd

New submission from Edd :

Hi,

I just had to move the "extern lstat..." outside the "ifndef
HAVE_LSTAT" to get python 2.6.1 to build on OpenBSD 4.4-current/i386.

I'm not suggesting this is correct, but it fixes the build for my
platform at least.

--- Modules/posixmodule.c.orig Fri Dec 12 11:08:54 2008
+++ Modules/posixmodule.c   Fri Dec 12 11:54:16 2008
@@ -208,10 +208,11 @@
 #ifdef HAVE_SYMLINK
 extern int symlink(const char *, const char *);
 #endif /* HAVE_SYMLINK */
+#endif /* !HAVE_UNISTD_H */
+
 #ifdef HAVE_LSTAT
 extern int lstat(const char *, struct stat *);
 #endif /* HAVE_LSTAT */
-#endif /* !HAVE_UNISTD_H */

 #endif /* !_MSC_VER */


Im using gcc-4.2

Thanks

--
components: Build
messages: 77667
nosy: vext01
severity: normal
status: open
title: Build failure on OpenBSD 4.4-current regarding lstat()
type: compile error
versions: Python 2.6

___
Python tracker 
<http://bugs.python.org/issue4639>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue17685] Frozenset literal?

2013-04-10 Thread Edd

New submission from Edd:

Hi,

I am willing to bet that this has been discussed before, but I don't see any 
related bugs.

I have been using Python for a while now as a prototyping language for 
scientific applications. Most recently I have been using it for prototype 
program analyses.

In this kind of work you are usually transcribing pseudo-code, defined in terms 
of sets, vectors and mappings into Python syntax. Inevitably, you need to store 
sets of sets, or you need to do some other operation that requires a hashable 
data structure.

As a result, I never use sets. I usually resort to using frozensets, which are 
hashable, yet the syntax for creating these is very verbose:

frozenset([e1, e2, ...])

To counter this, I usually use the following hack:

fs = frozenset

then frozensets can be instantiated like this:

fs([e1, e2, ...])

But this is not ideal. I can't help wondering why there is not a frozenset 
literal. I see that the mutable set recently got a literal, but why not 
frozenset?

Cheers!

--
components: Interpreter Core
messages: 186486
nosy: vext01
priority: normal
severity: normal
status: open
title: Frozenset literal?
type: enhancement

___
Python tracker 
<http://bugs.python.org/issue17685>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue21356] LibreSSL/RAND_egd fix needed.

2014-04-26 Thread Edd Barrett

New submission from Edd Barrett:

Hi,

I'm sure you have heard about OpenBSD's LibreSSL fork of OpenSSL. There has 
been a lot of code reorganisation and removal. One function which was removed 
`RAND_egd()` breaks the CPython build. CPython no longer builds on OpenBSD.

I have submitted a patch against PyPy already. The application library part of 
the change can probably be re-used since PyPy borrows CPython's 
application-level standard library (including the `ssl` and `socket` module). 
However, for the interpreter level change, the build system will probably have 
to be hacked. We need to check for the existence of `RAND_egd()` at configure 
time and only build in support if the function is found.

The PyPy patch (and some discussion) is here:
https://bitbucket.org/pypy/pypy/pull-request/233/fix-translation-for-libressl-and-fix-ssl/diff#comment-1744605

I may have a go at doing this myself (for Python-2.7 at least) if no-one steps 
up in the meantime; for now just making the CPython devs aware.

Thanks

--
components: Build
messages: 217198
nosy: Edd.Barrett
priority: normal
severity: normal
status: open
title: LibreSSL/RAND_egd fix needed.
versions: Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python 3.5

___
Python tracker 
<http://bugs.python.org/issue21356>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue19884] Importing readline produces erroneous output

2014-08-07 Thread Edd Barrett

Edd Barrett added the comment:

This problem shows up on OpenBSD too. It breaks 'hg view' also.

--
nosy: +Edd.Barrett

___
Python tracker 
<http://bugs.python.org/issue19884>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com