This is a combination question-and-status-report email. The question
would be, what does the "somewhat" tag mean on Solaris support in the
release notes for 3.0a1, and does someone have a list of things that
don't work, or does that just mean it hasn't been tested?
I built 3.0a1 on Sparc Solaris
On 2007-09-04, Georg Brandl wrote:
> I've added a basic skeleton of documentation for the "abc" module, but it
> would be nice if somebody proofread it and at add more from PEP 3119 if
> desired.
One strange point: the module correctly appears on the
library/python.html page (Python Runtime Servic
> First is whether the name of the function that returns the
> module-specific memory is PyModule_GetData() or PyModule_GetState()?
> The former is listed by the PEP but the latter is used by the example.
I think I like _GetState more, so I have now adjusted the PEP.
> Second is how are the excep
> This is a combination question-and-status-report email. The question
> would be, what does the "somewhat" tag mean on Solaris support in the
> release notes for 3.0a1, and does someone have a list of things that
> don't work, or does that just mean it hasn't been tested?
Not sure what "somewhat
I may not be the first to mistakenly write
class Foo(ABCMeta):
when I meant to write
class Foo(metaclass=ABCMeta):
but I'm sure I won't be the last.
Sorry for the mistake...
Maybe attempting to register an ABCMeta subclass might lead to a more
informative warning though?
--
On 9/5/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > This is a combination question-and-status-report email. The question
> > would be, what does the "somewhat" tag mean on Solaris support in the
> > release notes for 3.0a1, and does someone have a list of things that
> > don't work, or doe
On 9/5/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Yes; I'm not certain whether module reloading continues to be supported
> in Py3k or not. If not, it should be removed from the PEP, if yes, it
> should be specified.
I'm already missing the reload() builtin, so I think it should be kept
ar
On 9/4/07, Gregory P. Smith <[EMAIL PROTECTED]> wrote:
>
> On 9/4/07, Bill Janssen <[EMAIL PROTECTED]> wrote:
> > According to PEP 358, "bytes" will be in both 2.6 and 3.0. It would
> > be nice if the C API for "bytes" existed in the trunk, so that it
> > could be used for new code that will port
> Yes, this is a serious issue -- we are totally dependent on openssl
> for computing MD5 checksums. Several modules use MD5 checksums
> casually, and it's not good that these fail when openssl isn't
> available (or if it's too old, like what happened on an ancient Red
> Hat 7.3 system I have at ho
On 9/5/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> I think that's a serious issue to consider. As so much code now depends
> on OpenSSL, setup.py should try harder to find it. E.g. on the build
> slave, it can be found in /usr/sfw - not sure whether that is normal
> on a Solaris 10 installa
> Every OS I use has openssl installed so i figured someone else had made
> the same decision and removed the non-openssl variants. Are there
> really non-linux/bsd/osx installations out there where anyone intends to
> build and install python that do -not- have openssl installed
> somewhere?
Mo
> There is not. I can put OpenSSL in my environment
What do you "I can put". You compile it yourself? Why not use
the Sun-provided one?
> The
> 2.5 "What's new" documentation said that hashlib used OpenSSL when
> available, but it appears to be requiring OpenSSL?
That's for 2.5. In 3.0 (current
On 9/5/07, Gregory P. Smith <[EMAIL PROTECTED]> wrote:
[Guido]
> > Yes, this is a serious issue -- we are totally dependent on openssl
> > for computing MD5 checksums. Several modules use MD5 checksums
> > casually, and it's not good that these fail when openssl isn't
> > available (or if it's too
While we're at solaris, I would appreciate if some solaris expert(s)
could take a look at http://bugs.python.org/issue1777530
Thanks,
Thomas
___
Python-3000 mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-3000
Unsubsc
On 9/5/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On 9/5/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > > This is a combination question-and-status-report email. The question
> > > would be, what does the "somewhat" tag mean on Solaris support in the
> > > release notes for 3.0a1, and
>
> Also, the NIST SHA-1/256/384/512 code is freely available, there's
> also no reason to rely on OpenSSL for it (although it looks like the
> PKI reference implementation links that I can find are dead, so we
> might have to hunt a little bit).
>
> In either case, we could probably copy the relev
On 9/5/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On 9/5/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > Yes; I'm not certain whether module reloading continues to be supported
> > in Py3k or not. If not, it should be removed from the PEP, if yes, it
> > should be specified.
>
> I'm alr
Lisandro Dalcin wrote:
> Dear Travis, in my MPI wrappers, I use MPI_Alloc_mem function to get
> 'special' MPI memory, and next I return it to Python using
>
> return PyBuffer_FromReadWriteMemory(ptr, len);
>
> Well, getting back this rw-buffer in python, I tried to do
>
> mem = MPI.Alloc_mem(10)
On 9/5/07, Gregory P. Smith <[EMAIL PROTECTED]> wrote:
> No. OpenSSL hashlib support was added for a good reason. Its
> implementations are *much* faster as it includes platform optimized versions
> of all hash algorithms that are continually being updated tweaked and tuned.
> OpenSSL itself als
Neal, Anthony, Thomas W., and I have a spreadsheet that was started to
keep track of what needs to be done in what needs to be done in 2.6
for Py3K transitioning:
http://spreadsheets.google.com/pub?key=pCKY4oaXnT81FrGo3ShGHGg . I am
opening the spreadsheet up to everyone so that others can help
ma
test__locale (that's two underscores, testing _locale.c) fails on my
Red Hat 7.3 box. Further investigation shows that it's because the
et_EE locale (Estonia(n)) defines the thousands separator as '\xa0'
(no-break space U+00A0). Both localeconv() and nl_langinfo() use
PyUnicode_FromString() which a
21 matches
Mail list logo
