On Mon, Sep 10, 2007 at 07:37:02AM +0200, "Martin v. L?wis" wrote:
| In principle, it is possible to deal with these in ParseTuple.
| To do so:
| a) in configure.in, make a configure-time check to compute the
|size of the type, and possibly its signedness.
| b) in _cursesmodule.c, mak
Luke Mewburn schrieb:
> On Mon, Sep 10, 2007 at 07:37:02AM +0200, "Martin v. L?wis" wrote:
> | In principle, it is possible to deal with these in ParseTuple.
> | To do so:
> | a) in configure.in, make a configure-time check to compute the
> |size of the type, and possibly its signedness
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 10, 2007, at 1:30 AM, Paul Dubois wrote:
> The weekly summaries from the new bug tracker are disappearing
> somewhere
> between the tracker and python-dev. My attempt to post one by hand was
> rejected by python-dev-owner (Barry Warsaw?) with
On Monday 10 September 2007, Paul Dubois wrote:
> As a small boy I once knew wrote, I must not use bad words. (:->
It's OK to use them about Barry, though, surely?
*wave* Hi Barry.
--
Anthony Baxter, ekit. [EMAIL PROTECTED] (03) 9674 7015
Level 3 The Teahouse, 28 Clarendon St, Sth M
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 10, 2007, at 1:43 AM, Anthony Baxter wrote:
> On Monday 10 September 2007, Paul Dubois wrote:
>> As a small boy I once knew wrote, I must not use bad words. (:->
>
> It's OK to use them about Barry, though, surely?
>
> *wave* Hi Barry.
It's ok
> I have a change in my sandbox to explicitly avoid linking with 4.6.19
> but it seems like committing it would just pollute setup.py with vague
> notions of what versions of a specific library are bad. I'd prefer to
> just disallow use of libdb 4.6 completely in setup.py until oracle fixes
> this
> One, what *is* the scope of your
> amibition? I feel silly for asking, because I am pretty sure that
> somewhere in the beginning of this thread I missed either a proposal, a
> PEP reference, or a ticket number, but I've poked around a little and I
> can't seem to find it. Can you provide a
> I've now built a framework in test_ssl to test all client protocols
> (SSL2, SSL3, SSL23, TLS1) against all server protocols, and here's
> what I've come up with. Servers are along the X axis, and clients are
> on the Y axis. "Yes" means that that client protocol can talk to that
> server proto
Here's the updated connection table:
SSL2SSL3SS23TLS1
SSL2yes no yes no
SSL3yes yes yes no
SSL23 yes no yes no
TLS1no no yes yes
Given this, I think the client-side defaul
[EMAIL PROTECTED] wrote:
> Trent> If some would find it useful, here is a snippet of code that
> Trent> obfuscates email addresses for HTML as done by Markdown (a
> Trent> text-to-html markup translator). It randomly encodes each
> Trent> charater as a hex or decimal HTML entity (ro
People:
I modified my tool, whichs makes a summary of all the Python tickets
(I moved the source where the info is taken from SF to our Roundup).
In result, the summary is now, again, updated daily:
http://www.taniquetil.com.ar/facundo/py_tickets.html
Enjoy it.
Regards,
--
.Facundo
B
The Alpha/Tru64 buildbot seems to be having difficulty compiling
the _ssl.c file. Looks like missing header files. Anyone know what
the configuration of OpenSSL on that machine is like?
Bill
___
Python-Dev mailing list
Python-Dev@python.org
http://mail
The Solaris 10 buildbot is complaining about test_ssl, and I think
it's because some of the functions in it use constants from the ssl
module at the top level, i.e.,
def tryProtocolCombo (server_protocol,
client_protocol,
expectedToWork,
By the way, if you're offering to help with this, there are a couple
of things I could use some help with. I scratched my head a bit about
how to turn the "othername" possibility of a subjectAltName into a
Python data structure, using the OpenSSL C code, and finally gave up.
If you could provide a
> The Solaris 10 buildbot is complaining about test_ssl, and I think
> it's because some of the functions in it use constants from the ssl
> module at the top level, i.e.,
>
> def tryProtocolCombo (server_protocol,
> client_protocol,
> expect
On Sat, Sep 08, 2007, "Martin v. L?wis" wrote:
>
> No. IIUC, "expected skips" are a platform property. For your platform,
> support for threads is expected (whatever your platform is as log as
> it was built in this millenium).
Really? I thought NetBSD was still iffy WRT threading.
--
Aahz ([EMA
> The Alpha/Tru64 buildbot seems to be having difficulty compiling
> the _ssl.c file. Looks like missing header files. Anyone know what
> the configuration of OpenSSL on that machine is like?
Neal Norwitz and Ralf Grosse-Kunstleve have access to that machine.
Regards,
Martin
___
On Tuesday 11 September 2007, Martin v. Löwis wrote:
> > The Alpha/Tru64 buildbot seems to be having difficulty
> > compiling the _ssl.c file. Looks like missing header files.
> > Anyone know what the configuration of OpenSSL on that machine
> > is like?
>
> Neal Norwitz and Ralf Grosse-Kunstleve
>> No. IIUC, "expected skips" are a platform property. For your platform,
>> support for threads is expected (whatever your platform is as log as
>> it was built in this millenium).
>
> Really? I thought NetBSD was still iffy WRT threading.
Ah, right. Still, it seems that people expect that thre
> > Neal Norwitz and Ralf Grosse-Kunstleve have access to that
> > machine.
>
> Neal's on leave all this month, I believe.
Well, I'm not sure it's urgent. Are there lots of Alphas still
running? And Tru64 is in end-of-life mode.
Bill
___
Python-Dev m
Hi all,
I have an unusual use case in which some software I work on compiles a
version of Python for distribution. I'm not 100% across this as it's not at
all my area of responsibility, but I have been having some issues lately.
My hand-compiled version of Python 2.5 works just fine, and in turn
21 matches
Mail list logo
