John Levon added the comment:
That's a little abrupt. Whilst it would be nice if the compiler had a correct
return value, it occurs with multiple compilers, and I pointed
you to a suitable workaround Python could employ. Even if Studio gets fixed,
there are previous releases out there
John Levon added the comment:
Even worse, a nasty hack was added just for Intel's compiler as seen in
http://bugs.python.org/issue1162001
--
___
Python tracker
<http://bugs.python.org/iss
John Levon added the comment:
Anatoly, see above. We have done exactly that. (Honestly, when I first wrote
the changes, I saw them as too hacky to ever be accepted upstream).
This name change seems frivolous and will indeed break existing scripts
John Levon added the comment:
This is not a bug in Solaris - the interfaces Python is trying to use are not
standardized.
(It's a reasonable RFE for Solaris to fully support these, though - I'll follow
up on that.)
WRT the patch, at least the PACKET_* defined would be better
John Levon added the comment:
The posted patch: better if the PACKET_* tests were just at the two missing
ones rather than removing all of the ones that are actually there like
PACKET_OUTGOING.
--
___
Python tracker
<http://bugs.python.
John Levon added the comment:
configure.in has:
AC_MSG_RESULT([$with_dtrace])
...
AC_MSG_RESULT($with_dtrace)
Why twice? It looks confusing.
--
___
Python tracker
<http://bugs.python.org/issue4
John Levon added the comment:
Jesus, yes, it's totally possible that POSIX might define:
(stat.S_IFSOCK + stat.S_IFIFO)
to mean something other than S_IDOOR. However, the POSIX committee
is always careful to respect existing usage. It's vanishingly unlikely
that any attempt to do
Changes by John Levon :
--
nosy: +movement
___
Python tracker
<http://bugs.python.org/issue7946>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by John Levon <[EMAIL PROTECTED]>:
--
nosy: +movement
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue4434>
___
___
Python
John Levon <[EMAIL PROTECTED]> added the comment:
Besides, .so files should always declare their dependencies.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
John Levon <[EMAIL PROTECTED]> added the comment:
If Ubuntu wants to deliver a static libpython, it also needs to deliver
static versions of the Python modules, or accept that they're not usable
from a static libpython.
It makes no sense at all to mix libpython.a with these .so fil
John Levon added the comment:
This issue also affects Solaris (and in particular xend is broken). Is
there a reason bamby's fix isn't yet applied?
--
nosy: +movement
title: signals in thread problem -> signals not always delivered to main
thread, since other threads ha
John Levon added the comment:
Yes, Python guarantees the behaviour under discussion:
http://docs.python.org/library/signal.html
___
Python tracker
<http://bugs.python.org/issue1
Changes by John Levon :
--
nosy: +movement
___
Python tracker
<http://bugs.python.org/issue4111>
___
___
Python-bugs-list mailing list
Unsubscribe:
John Levon added the comment:
I haven't seen "shorter than expected" message before, sounds like a Mac
OS X specific thing.
As for never getting any probes out, this is where it gets fun.
Debugging this is very tricky indeed: it involves you dropping into the
kernel debugger and
Changes by John Levon :
--
nosy: +movement
___
Python tracker
<http://bugs.python.org/issue4609>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by John Levon :
--
nosy: +movement
___
Python tracker
<http://bugs.python.org/issue3928>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by John Levon :
--
nosy: +movement
___
Python tracker
<http://bugs.python.org/issue3265>
___
___
Python-bugs-list mailing list
Unsubscribe:
John Levon added the comment:
Just came across this bug.
_XOPEN_SOURCE_EXTENDED isn't the only sticking point here: neither XPG3
nor XPG4 have C99 either: _XOPEN_SOURCE (at least with a value below
600) is definitely wrong. To quote the header:
"346 * It is invalid to compile an
John Levon added the comment:
Yep, this is an annoying misfeature of Sun Studio. There is no way to
affect this behaviour. There is a Sun Studio bug filed for this
(-errwarn should affect this behaviour, but it doesn't).
Here's some example m4 that libvirt uses to check this cas
Changes by John Levon :
--
nosy: +movement
___
Python tracker
<http://bugs.python.org/issue976613>
___
___
Python-bugs-list mailing list
Unsubscribe:
John Levon added the comment:
Python should define *only* __EXTENSIONS__, not the others, as Zooko
already mentioned, for the reasons he mentioned. I'm not sure how you
got a different impression from what I or he said.
___
Python tracker
John Levon added the comment:
Zooko, the patches are available here:
http://src.opensolaris.org/source/xref/jds/spec-files/trunk/patches/
> Then you were arguing that defining _XOPEN_SOURCE is wrong if the value
Actually, I was saying that below that value simply won't work
Change by John Levon :
--
nosy: +movement
___
Python tracker
<https://bugs.python.org/issue37790>
___
___
Python-bugs-list mailing list
Unsubscribe:
John Levon added the comment:
closefrom() is on both Solaris and illumos too - and might even have originated
there as an API - so if that's the issue, it should be trivially fixable
--
___
Python tracker
<https://bugs.python.org/is
John Levon added the comment:
I checked, and the supposition this is due to lack of closefrom() doesn't seem
to be correct. Running the test case and looking at 'truss' output, there is no
large number of close() that one would expect if this was the issue.
I don't se
John Levon added the comment:
I would strongly suggest those of you who are not "getting it" to actually try
Jesus's patch out in some real scenarios. You'll quickly see what the benefit
is. I think some of you are missing that it's a *not* just about performance:
it
John Levon added the comment:
Any progress on this regression? A patch is available... thanks.
--
___
Python tracker
<http://bugs.python.org/issue1975>
___
___
John Levon added the comment:
The spec broken is here:
http://docs.python.org/library/signal.html
Namely:
# Some care must be taken if both signals and threads are used in the
same program. The fundamental thing to remember in using signals and
threads simultaneously is: always perform
John Levon added the comment:
I still do not understand the objection you have to the simple patch
which restores old behaviour, works the same across all OSes, and
doesn't require new APIs. What is the objection?
--
___
Python tracker
John Levon added the comment:
To quote Andriy in the first comment:
"It doesn't bring any visible changes to readline behavior either."
Are you saying this is not the case?
--
___
Python tracker
<http://bugs.py
John Levon added the comment:
> However, experience tells that systems can break in surprising ways
> if the system headers are compiled with different defines.
This is indeed a reasonable concern (for which the best solution is
dropping the defines in the Python compile).
> I do
John Levon added the comment:
Surely readline is irrelevant anyway. The Python spec guarantees
behaviour, and that guarantee is currently broken.
___
Python tracker
<http://bugs.python.org/issue1
John Levon added the comment:
Robert, I have no idea how Mac OS does pstack helpers without generating
object files, sorry.
> no simply pid$target:a.out:: probes available.
Hmm. Try adding -Z to see if that helps.
> /Users/rkern/hg/Python-2.5.4/Include/phelper.d: line 110: relo
John Levon added the comment:
Yes, my mistake. I noticed this typo in the original patch:
207 +PyObject *
208 +PyEval_EvalFrameexEx(PyFrameObject *f, int throwflag))
Can you:
- verify that HAVE_DTRACE is indeed defined for ceval.c
- do an nm on ceval.o and look which Eval
John Levon added the comment:
This appears to be one of the few cases where there's incompatibilities between
different versions of the standards. Old BSD sockets use msg_accrights*,
whereas the more modern way is msg_control*
pointing to a struct cmsghdr.
In terms of user/kernel inte
John Levon added the comment:
Right, it should be one of the "official" ways of enabling that.
--
___
Python tracker
<http://bugs.python.org/issue8864>
___
__
John Levon added the comment:
defining _XOPEN_SOURCE=600 or similar is better, as Martin pointed out.
--
___
Python tracker
<http://bugs.python.org/issue8
John Levon added the comment:
Yes, we would almost certainly want something similar.
--
___
Python tracker
<http://bugs.python.org/issue8864>
___
___
Python-bug
John Levon added the comment:
It's not clear why you'd need configure tests, but you could easily add the
define in the body of the autoconf test AFAIK - is there a reason this is
difficult?
--
___
Python tracker
<http://bugs.python.
John Levon added the comment:
Terry, what in the above discussion leads you to believe there is no bug?
The original complaint "Python cannot be embedded in shared library due to
dependency problems with lib-dynload" is still valid.
--
status: pendi
41 matches
Mail list logo
