> Applink is roughly explained at
> http://www.openssl.org/support/faq.html#PROG2. The matter was discussed
> about half a year ago but no decision was made. See
> http://mail.python.org/pipermail/python-dev/2008-March/077424.html
>
> applink.c is just a table of integer constants to function poin
Greg writes:
> Mark Hammond wrote:
>
> > The only conflict I see here is the requirement to install into
> "\Program Files"
>
> Doesn't that just mean that if an OEM decides to preinstall it,
> they need to put it in Program Files? They're at liberty to
> do that.
I'm not very familiar with the
Martin v. Löwis wrote:
All, and not to start flames, but I still do not understand why
applink.c isn't included in python's main (conditionally) instead of
expecting users, many of them novices, to do the build. ???
One reason is that I don't know what applink is, and why I should
care about i
Mark Hammond wrote:
The only conflict I see here is the requirement to install into "\Program
Files"
Doesn't that just mean that if an OEM decides to preinstall it,
they need to put it in Program Files? They're at liberty to
do that.
--
Greg
___
Pyt
Dear All,
Apologies that web site was not working earlier. I believe that I've now fixed
it. The patch can still be found at
http://www.cats-muvva.net/software/Python-taint-diff-3.0rc3.tar.bz2.
CatsMuvva
___
Python-Dev mailing list
Python-Dev@python.o
Bugbee, Larry wrote:
As I recall, OpenSSL, a long while ago stopped, supporting some idiosyncrasies
> associated with Windows I/O and opted for a "cleaner" approach, that of
requiring
developers to link a small file, applink.c, into the app's main.
Could it not be linked into the openssl ext
Nick Coghlan wrote:
i.e.
"from foo.bar import baz" >
= __import__('foo.bar', globals(), locals(), ['baz'], -1)
baz = .baz
When there are multiple names being imported or an 'as' clause is
involved, I hope the reasons for doing it this way become more obvious:
"from foo.bar import baz, bo
> > > All, and not to start flames, but I still do not understand why
> > > applink.c isn't included in python's main (conditionally) instead
> > > of expecting users, many of them novices, to do the build. ???
> >
> > One reason is that I don't know what applink is, and why I should care
> >
Mart Somermaa wrote:
__import__('foo.bar', globals(), locals(), ['baz'], -1)
>
>
> i.e. 'bar' is imported, not 'baz' (or 'ham' and not 'eggs').
You're reading it wrong. 'baz' *is* imported, but 'bar' is returned from
the function call. You will find that the import statement generates
some
I've created http://bugs.python.org/issue4448 to track this issue.
On Thu, Nov 27, 2008 at 6:50 AM, Kristján Valur Jónsson <
[EMAIL PROTECTED]> wrote:
> I came across this in socket.c:
>
> # _rbufsize is the suggested recv buffer size. It is *strictly*
>
> # obeyed within readli
I am not at all a windows person but I have used
http://www.dennisbareis.com/makemsi.htm in the past to automate editing and
tweaking some MSI files for testing. It can also be used to generate new
ones. It looks like it would still require something to generate its own
input description. Regard
Dear All,
I found I needed support for taint mode in python and have done some work to
realise this. It's by no means complete at this time, but I'm floating this
idea on this group to see how much interest there is.
The implementation is pretty simple:
- an extra field in PyObject to maintain
Update: it looks like IEEE 754-1985 does require that
roundtripping works, at least when the rounding mode
is round-to-nearest. From section 5.6 again:
"""
When rounding to nearest, conversion from binary to decimal and back to
binary shall be the identity as long as the decimal string is carried
Torne,
Many thanks for your input!
> IEEE 754 doesn't include string formatting or parsing as far as I know,
> so I think this is irrelevant to whether we are compliant :)
I think IEEE 754 is relevant. :-)
There's a section 5.6 in the original 1985 standard that's called
something like: "Binar
On Thu, Nov 27 08 at 3:58:43PM +0100, Christian Heimes wrote:
> A while ago I contacted Jukka Laurila from the Nokia developer board
> about IEEE 754 support on S60 phones. The information from Jukka may be
> useful for future reference.
OK, I want to weigh in here, but first I need a lil dis
Mart Somermaa wrote:
There at least two workarounds:
* the getattr approach documented in [3]
I can't comment on the rest, but the getattr seems overly complicated.
If you need just the module, what's wrong with:
__import__(modname)
modobj = sys.modules[modname]
___
Python programmers need to dynamically load submodules instead of
top-level modules -- given a string with module hierarchy, e.g.
'foo.bar.baz', access to the tail module 'baz' is required instead
of 'foo'.
Currently, the common hack for that is to use
modname = 'foo.bar.baz' mod = __import__(m
Giovanni Bajo wrote:
> On gio, 2008-11-27 at 00:29 +0100, "Martin v. Löwis" wrote:
>>> So, deducing from your reply, this "merge module" is a thing that allows
>>> to install the CRT (and other shared components)?
>> Correct. More generally, a merge module is a something like an MSI
>> library (.a
A while ago I contacted Jukka Laurila from the Nokia developer board
about IEEE 754 support on S60 phones. The information from Jukka may be
useful for future reference.
Christian
Original Message
Subject: Re: Python 2.6/3.0, IEEE 754 floating point semantics and S60
We've b
I came across this in socket.c:
# _rbufsize is the suggested recv buffer size. It is *strictly*
# obeyed within readline() for recv calls. If it is larger than
# default_bufsize it will be used for recv calls within read().
What I worry about is the readline() case. Is t
On gio, 2008-11-27 at 00:29 +0100, "Martin v. Löwis" wrote:
> > So, deducing from your reply, this "merge module" is a thing that allows
> > to install the CRT (and other shared components)?
>
> Correct. More generally, a merge module is a something like an MSI
> library (.a). It includes a set o
On 2008-11-27 04:12, Bugbee, Larry wrote:
> Not necessarily. I have no problems with hashlib or Python/M2Crypto/OpenSSL
> as long as I'm doing memory-oriented operations. It is only when the
> function does I/O that errors occur. ...like reading/writing a PEM file,
> randpool.dat, etc.
FWI
22 matches
Mail list logo
