Ronald Oussoren added the comment:
FWIW, I've filed an issue with Apple for this: Radar #7330231
--
___
Python tracker
<http://bugs.python.org/issue7085>
___
___
Changes by Ronald Oussoren :
--
status: pending -> closed
___
Python tracker
<http://bugs.python.org/issue3962>
___
___
Python-bugs-list mailing list
Unsubscri
Ronald Oussoren added the comment:
Closing the issue as this is not a bug in python (as noted in the
comments) and there doesn't seem to be a workaround for avoiding the
spurious messages on stderr.
--
resolution: -> wont fix
status: open -> closed
type: crash
Ronald Oussoren added the comment:
The crash is caused by loading any extension that happens to link with
CoreFoundation on a secondary thread, unless CoreFoundation was already
initialized.
The CF framework contains a constructor that explicitly aborts when it
is not called on the main
Ronald Oussoren added the comment:
The crash is caused by loading any extension that happens to link with
CoreFoundation on a secondary thread, unless CoreFoundation was already
initialized.
The CF framework contains a constructor that explicitly aborts when it
is not called on the main
Ronald Oussoren added the comment:
I committed a fix in r76403 (trunk), r76404 (2.6), r76405 (3.2), 76406
(3.1)
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/
Ronald Oussoren added the comment:
I've just committed a fix for this issue in all 4 active branches (2.6,
2.7, 3.1 and 3.2)
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python
Ronald Oussoren added the comment:
The problem occurs in two occassions:
1) python was configured/built without the Carbon bindings (such
as the copy that Apple ships)
2) python was build in 64-bit mode
In both cases Carbon.File does not have an FSSpec type.
Luckily this has already been
Ronald Oussoren added the comment:
Fixed the postflight issue in r76407 (trunk), r76408 (2.6), r76409 (3.2)
and r76410 (3.1).
--
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bug
Changes by Ronald Oussoren :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue6393>
___
___
Python-bugs-list mailing list
Unsubscri
Ronald Oussoren added the comment:
<http://www.opengroup.org/onlinepubs/9699919799/functions/printf.html>
claims fprintf should return a negative value when there is an output
error (the same claims is in the manpage of fprintf on OSX 10.6).
Neither document refers to the error ind
Ronald Oussoren added the comment:
According to
<http://developer.apple.com/legacy/mac/library/documentation/Carbon/Concep
tual/Carbon_Event_Manager/CarbonEvents.pdf> this issue is valid.
However, I won't work on fixing this because Carbon is deprecated, both
the Python bindi
Changes by Ronald Oussoren :
--
resolution: -> wont fix
versions: +Python 2.6, Python 2.7
___
Python tracker
<http://bugs.python.org/issue822005>
___
___
Py
Ronald Oussoren added the comment:
Lowering the priority to low because this is a bug in a deprecated binding
for a deprecated Apple framework. I won't work on a fix, although I am
willing to review and apply a patch when someone provides one.
--
nosy: +ronaldoussoren
pri
Ronald Oussoren added the comment:
In most shells $PWD is a magic variable that is maintained by the shell
itself.
IMHO python has no reason to mess with variables that happen to be defined
by some shells. If subprocess were to set $PWD, os.setuid should set $UID,
and there may be other
Ronald Oussoren added the comment:
On 26 Nov, 2009, at 19:27, Geoffrey Bache wrote:
>
> Geoffrey Bache added the comment:
>
> I can see your point, though I think particularly in this case it's
> (unfortunately) fairly common that scripts on POSIX platforms read $PWD
Ronald Oussoren added the comment:
I agree with martin, this is probably an OS bug.
BTW. I can confirm that the issue occurs on OSX 10.6 as well (using the
binary 2.6.4 installer on the python.org website).
I might get around to writing a C equivalent of the script in the future,
but
Ronald Oussoren added the comment:
Hugh, for us as Python maintainers there is a distinction between issues
with the Python implementation itself and those outside of Python. The
former we can solve, the latter not.
At best we can work around issues in the environment (I've rec
Ronald Oussoren added the comment:
Hugh: Do you have an ADC account (either free or payed)? If you do you can
file bugs at http://bugreport.apple.com/. If you don't I can file the bug
for you.
--
___
Python tracker
<http://bugs.py
Ronald Oussoren added the comment:
I'm currently testing a patch that adds the required SIZEOF_ macros to
pymacconfig.h, simular to how SIZEOF_LONG and SIZEOF_VOIDP are handled.
I expect to commit a fix later today to the 2.7 and 3.2 branches. The new
SIZEOF_ macros are only needed fo
Ronald Oussoren added the comment:
Hugh: why did you remove the .c file?
I'd prefer to keep the .c file in the python tracker as, just in case
someone else runs into the same issue and starts debugging the issue.
--
___
Python tracker
Ronald Oussoren added the comment:
Hugh: never mind
There is a workaround for this issue: use socketpair(2) instead of
pipe(2). I haven't thought enough about the consequences yet to have an
firm opinion on implementing os.pipe using socketpair(2) on OSX. My gut
feeling is th
Ronald Oussoren added the comment:
Fixed in r76623 (trunk) and r76624 (3.2).
(The commit message mentions another issue, that's a copy-paste error on
my end)
--
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
Changes by Ronald Oussoren :
--
assignee: glyph -> ronaldoussoren
nosy: +ronaldoussoren
___
Python tracker
<http://bugs.python.org/issue2441>
___
___
Python-
Ronald Oussoren added the comment:
Could you also post the generated pyconfig.h?
--
___
Python tracker
<http://bugs.python.org/issue7452>
___
___
Python-bug
Ronald Oussoren added the comment:
The problem shouldn't be present in 3.1 and 2.7, both trees no longer
contain the ancient documentation files.
IMHO the best fix is to remove
Mac/Resources/app/Resources/English.lproj/Documentation/ide/ (and the
link to ide/index.html in .../Document
Ronald Oussoren added the comment:
This is due to a block starting at '#ifdef HAVE_GCC_ASM_FOR_X87' in
Python/pymath.c.
A simple patch to pymacconfig.h fixes the issue, I'll commit it once I've
fully tested the result.
--
__
Ronald Oussoren added the comment:
Fixed in r76712 (trunk), r76713 (3.2), r76714 (3.1).
The python3 branches contained about half of the fix, I merged the trunk
version into python3 anyway to keep all 3 branches in sync.
The issue does not affect the 2.6 branch.
--
resolution
Ronald Oussoren added the comment:
This should be fixed in r76715, I've removed the documentation that caused
the installer issues in the first place.
--
resolution: -> fixed
stage: -> test needed
status: open -> pending
type
Changes by Ronald Oussoren :
--
assignee: ronaldoussoren ->
___
Python tracker
<http://bugs.python.org/issue6800>
___
___
Python-bugs-list mailing list
Un
Ronald Oussoren added the comment:
Is this issue still relevant? I cannot reproduce this on my machines.
--
nosy: +ronaldoussoren
___
Python tracker
<http://bugs.python.org/issue3
Changes by Ronald Oussoren :
--
status: pending -> closed
___
Python tracker
<http://bugs.python.org/issue7190>
___
___
Python-bugs-list mailing list
Unsubscri
Ronald Oussoren added the comment:
richard: could you please elaborate on what you think is wrong?
readline doesn't get build because OSX' libedit isn't good enough
for the readline module in 2.6, this is fixed in 2.7.
On my machine the other ones do get build, althoug
Ronald Oussoren added the comment:
Ned: which version of Python do you build? The issue was only in the
trunk (2.7), the other branches were fine (although the code in 3.1 and
3.2 was suboptimal). BTW. The issue affected universal builds on all OSX
versions.
The trunk should be fine now as
Ronald Oussoren added the comment:
Ned: the best way to ensure universal builds don't get broken is through
the buildbots. AFAIK there are no buildbots that create universal
binaries at the moment. Sadly enough I don't have the resources to
provide one.
Mark: Mac/README expla
Ronald Oussoren added the comment:
BTW. Am I correct when I state that this issue has been fixed and can be
closed?
--
___
Python tracker
<http://bugs.python.org/issue7
Ronald Oussoren added the comment:
FWIW: I now have a 2.7 tree with the new pythonw on my machine, open
issues are:
* Ensure IDLE.app gets build in such a way that the GUI works for
all supported universal binaries (including a 4-way build on 10.5,
where the system Tk doesn't work
Ronald Oussoren added the comment:
I agree that _scproxy should be ported to the 3.x trees. Such a port
should be fairly straightforward, but is harder than just copying files
over due to the str/unicode changes in the 3.x tree.
--
___
Python
Changes by Ronald Oussoren :
--
priority: normal -> low
___
Python tracker
<http://bugs.python.org/issue1123727>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Ronald Oussoren :
--
assignee: -> ronaldoussoren
nosy: +ronaldoussoren
___
Python tracker
<http://bugs.python.org/issue3363>
___
___
Python-bugs-lis
New submission from Ronald Oussoren :
I haven't checked the 3.1, 2.7 and 2.6 documentation, but at least for 3.2
the documentation of PyErr_Format lists a very small number of supported
format characters compared to PyUnicode_FromFormat even though
PyErr_Format calls PyUnicode_FromForma
Ronald Oussoren added the comment:
I don't agree that the current binaries are only useful for Tiger and
earlier, the binaries work just fine on Leopard and Snow Leopard as
well.
FWIW. I'm planning to provide a 3-way universal binary, or even just
intel (i386, x86_64) for Python 2
Changes by Ronald Oussoren :
--
resolution: -> accepted
stage: -> needs patch
title: x84_64 arch Missing from 2.6.4 Mac universal binaries - Cripples
building embedded 64-bit -> Compile error when building a 3-way universal
framework when a 2-way universal framework i
Changes by Ronald Oussoren :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue7452>
___
___
Python-bugs-list mailing list
Unsubscri
Ronald Oussoren added the comment:
This issue is for deprecated Carbon module that has a well-maintained
alternative outside of the stdlib.
--
resolution: -> wont fix
stage: test needed -> committed/rejected
status: open -> closed
_
Ronald Oussoren added the comment:
What do you use LINKFORSHARED for?
As a minor rant: the wholesale export of all settings in the main
Makefile through distutils sucks big time. I have no idea whether or not
LINKFORSHARED is meant to be a public API, and if it is what it should
be used for
Ronald Oussoren added the comment:
python-config (or python3-config for python 3.x) is the best way to get
this information in recent versions of python (IIRC 2.6 or newer)
--
___
Python tracker
<http://bugs.python.org/issue3
Ronald Oussoren added the comment:
To be honest: I don't know.
Tarek: do you think LINKFORSHARED should contain a value that works
outside of Python's build environment?
--
___
Python tracker
<http://bugs.python.
New submission from Ronald Oussoren :
Include/unicodeobject.h includes prototypes for PyUnicode_FromFormat and
PyUnicode_FromFormatV in both 2.6 and 2.7, but those functions are not
included in the documention.
And worse, the implementation contains bugs: the %R format code tries to
include
Ronald Oussoren added the comment:
I've committed the completed patch as r77031 (trunk) and r77032 (py3k)
I will not backport to 2.6 and 3.1 because this is not a bugfix.
--
resolution: -> accepted
stage: needs patch -> committed/rejected
status: ope
Ronald Oussoren added the comment:
Fixed in r77033 (trunk), r77034 (2.6), r77035 (py3k), r77036 (3.1)
Development on the 2.5 tree is closed, I will therefore not backport to
2.5.
As a workaround you can add -Wl,-search_paths_first to the linker flags to
ensure that the libpython.a in the
Ronald Oussoren added the comment:
This is no longer an issue: the Info.plist is now initialized by the build
process and includes the correct version number. At the time the bug was
files the plist needed to be updated manually and that didn't always
happen (or rather, more often tha
New submission from Ronald Oussoren :
When running GCC with warnings the compiler can warn about incomplete
structure initializers. This gives spurious warnings when initializing a
PyModuleDef structure using PyModuleDef_HEAD_INIT
The attached patchs changes PyModuleDef_HEAD_INIT to
Changes by Ronald Oussoren :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue1700507>
___
___
Python-bugs-list mailing list
Unsubscri
Ronald Oussoren added the comment:
Is patch this still relevant?
The functionality seems to be present in the trunk and py3k.
--
nosy: +ronaldoussoren
___
Python tracker
<http://bugs.python.org/issue2
Ronald Oussoren added the comment:
This issue is fixed in the 2.7 and 3.2 trees.
I'm therefore closing this issue.
--
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.pyt
New submission from Ronald Oussoren :
The documentation for bf_getbuffer at <http://www.python.org/doc/3.1/c-
api/typeobj.html#buffer-object-structures> claims:
The signature of getbufferproc is int (PyObject *obj, PyObject *view,
int flags). obj is the object to export, view is the Py_
Ronald Oussoren added the comment:
Another buffer documentation buglet is the documentation for
'PyBuffer_FillInfo'. The prototype in the documentation is:
int PyBuffer_FillInfo(Py_buffer *view, void *buf, Py_ssize_t len, int
readonly, int infoflags)
The real prototype has an
Ronald Oussoren added the comment:
AFAIK This is already fixed in the repository.
I don't have time to verify this right now, but will do so later this week
(which is why I'm assigning the issue to myself)
--
assignee: tarek -> r
Ronald Oussoren added the comment:
I forgot to mention the workaround for the 3.1 release: reinstall XCode
and make sure that you don't do the default install, but select the 10.4u
SDK for installation as well.
You may then run into linking issues, they only workaround for that is to
Ronald Oussoren added the comment:
I will look at this in the weekend.
--
___
Python tracker
<http://bugs.python.org/issue7591>
___
___
Python-bugs-list mailin
Ronald Oussoren added the comment:
Ned: the new functionality is also needed for 2-way univeral binaries, it makes
pythonw behave much more as if you execute the real interpreter instead of a
stub executable.
That posix_spawn doesn't exist sucks, and I'm a bit annoyed with myse
Ronald Oussoren added the comment:
BTW. The patch is incorrect in it current form:
* The change to LIPO_32BIT_FLAGS is unconditional, the current values are
needed to build on modern system, I guess the proposed new value would be
needed for building on 10.4?
* The patch changes pythonw to
Ronald Oussoren added the comment:
I've attached a patch that should fix the build issues with the 10.4 SDK.
The patch touches configure.in, run autoconf and autoheader after applying the
patch.
I haven't tested the patch yet beyond compilation on 10.6 system without the
10.4 S
Ronald Oussoren added the comment:
As Ned noted you probably have installed GNU gettext in /usr/local and that
copy does not contain both intel architectures (i386 and x86_64)
There's nothing we can do about that, I have tried to find a way to exclude
non-system locations from the de
Ronald Oussoren added the comment:
Ned and Sridhar: IMO we need a configure test to detect which argument should
be used to extract ppc code (ppc or ppc7400).
--
___
Python tracker
<http://bugs.python.org/issue7
Ronald Oussoren added the comment:
abspath is basically dead code in macpath, the module is used to manipulate
classic MacOS9-style paths and is no longer used as os.path on any supported
platform (it used to be os.path on MacOS9).
BTW. the module itself is not dead, OSX still uses OS9-style
Ronald Oussoren added the comment:
I'm closing this as "wont fix" because the Carbon bindings are deprecated
and are removed in Python 3.0.
--
nosy: +ronaldoussoren
resolution: -> wont fix
status: open -> closed
___
Ronald Oussoren added the comment:
Closing as "won't fix" because the Carbon bindings are deprecated, and
FSSpec's are even more deprecated (they're even deprecated at the C-level)
--
nosy: +ronaldoussoren
resolution: -> won
Ronald Oussoren added the comment:
Closing as "won't fix" because the aepack module is deprecated and has
various other major issues on little-endian systems.
--
nosy: +ronaldoussoren
resolution: -> wont fix
status: open -> closed
_
Ronald Oussoren added the comment:
Closing as won't fix because the Carbon modules are deprecated.
This doesn't actually affect behaviour of the Carbon bindings, other than
causing an icon to appear on the dock which is basicly purely cosmetical.
--
nosy: +ronaldoussoren
Ronald Oussoren added the comment:
Carbon.CF is very imcomplete. Use PyObjC instead.
--
nosy: +ronaldoussoren
resolution: -> wont fix
status: open -> closed
___
Python tracker
<http://bugs.python.org/is
Ronald Oussoren added the comment:
Fixing this isn't worth the trouble.
--
nosy: +ronaldoussoren
resolution: -> wont fix
status: open -> closed
___
Python tracker
<http://bugs.python.o
Ronald Oussoren added the comment:
Closing as won't fix. The "Make Applet" tool is still present, but rather
useless.
Use py2app to create application bundles.
--
nosy: +ronaldoussoren
resolution: -> wont fix
status: open -> closed
_
Changes by Ronald Oussoren :
--
assignee: -> ronaldoussoren
nosy: +ronaldoussoren
___
Python tracker
<http://bugs.python.org/issue974159>
___
___
Python-
Ronald Oussoren added the comment:
I've reapplied the hack.
I'm closing the issue because we will not regenerate the Carbon bindings
as these are deprecated and are no longer present in Python 3.x
--
nosy: +ronaldoussoren
resolution: later -> fixed
status: o
Ronald Oussoren added the comment:
Is this a standard unix build or a framework build?
___
Python tracker
<http://bugs.python.org/issue5408>
___
___
Python-bugs-list m
Ronald Oussoren added the comment:
I don't have time to investigate this right now, I do have access to a
10.5 server box though. With some luck I'll be able to create a patch
later today.
Looking at the code in urllib I found the most likely reason for the
problem: the Python sc
Changes by Ronald Oussoren :
--
nosy: -ronaldoussoren
___
Python tracker
<http://bugs.python.org/issue1201569>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ronald Oussoren added the comment:
This is now also fixed for the trunk and 2.6
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/iss
Ronald Oussoren added the comment:
Fixed for the trunk and 2.6 as well.
--
resolution: accepted -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/
Ronald Oussoren added the comment:
Fixed for the trunk and 2.6 as well.
--
resolution: accepted -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/
Ronald Oussoren added the comment:
I've applied a cleaned up version of patch-nad0014-trunk-26.txt to the
trunk and 2.6 branch. This completely fixes this issue.
--
resolution: accepted -> fixed
status: open -> closed
___
Python tra
Ronald Oussoren added the comment:
I'm closing this issue as rejected because the macostools module is
deprecated. We'll therefore not apply any more feature enhancements.
--
nosy: +ronaldoussoren
resolution: -> rejected
status: o
Ronald Oussoren added the comment:
Ned: IMHO your patch is not correct. test_osx_env tests behaviour that's
only valid for a framework build, and should therefore only run when
testing a framework build.
The easiest way to accomplish that is to change the test in
test_osx_env.ma
Ronald Oussoren added the comment:
I intend to close this as won't fix. The issue is caused by Apple's build
of Python, the generic Python.org build won't even compile when using
libedit.
___
Python tracker
<http://bugs.py
Ronald Oussoren added the comment:
Skip: could you please explain which bit of Xcode you didn't install?
The compile should work regardless of installing 10.3 SDK support.
The code you mention in your report sets MACOSX_DEPLOYMENT_TARGET to
10.3 on 10.3 systems or later, unless you expl
Changes by Ronald Oussoren :
--
nosy: +ronaldoussoren
___
Python tracker
<http://bugs.python.org/issue5154>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ronald Oussoren added the comment:
I'm +1 on this feature, I haven't looked at the patch yet.
--
nosy: +ronaldoussoren
___
Python tracker
<http://bugs.python.
Changes by Ronald Oussoren :
--
assignee: -> ronaldoussoren
___
Python tracker
<http://bugs.python.org/issue5269>
___
___
Python-bugs-list mailing list
Un
Ronald Oussoren added the comment:
AFAIK this patch is no longer necessary, at least no on OSX. The current
binary installer is already build using a separate DESTDIR without having
to patch Makefiles.
--
nosy: +ronaldoussoren
___
Python tracker
Ronald Oussoren added the comment:
IMHO fixing this is not worth the trouble, we should just document that
the Carbon extensions aren't supported in a UCS4 build (or even explictly
detect a UCS4 build in setup.py and not compile the Carbon extensions).
--
nosy: +ronaldous
Ronald Oussoren added the comment:
Usage of PyObjC in the build-script should be avoided, as should eating
exceptions like you propose. The rationale for not silencing exceptions is
that the build script is supposed to enable reproducable builds.
I'll probably add a small Cocoa ObjC pr
Changes by Ronald Oussoren :
--
assignee: -> ronaldoussoren
___
Python tracker
<http://bugs.python.org/issue4848>
___
___
Python-bugs-list mailing list
Un
Ronald Oussoren added the comment:
I intend to close this issue as it is an enhancement proposal for a
deprecated module.
Py2app (the modern replacement for bundlebuilder) also doesn't support
this scenario, although it should be fairly easy to add such support to
that cod
Ronald Oussoren added the comment:
Fixed in the trunk in revision r70178.
hhas: it is save to backport this to python 2.6?
--
assignee: jackjansen -> ronaldoussoren
nosy: +ronaldoussoren
resolution: -> accepted
___
Python tracker
Ronald Oussoren added the comment:
poll(3) doesn't work for all types of filedescriptors on OSX.
Specifically:
BUGS
The poll() system call currently does not support devices.
(That's from the manpage of poll). This is why Apple doesn't expose
select.poll in their buil
Ronald Oussoren added the comment:
Committed my fix as r70179 (3.x) and r70180 (30-maint).
Benjamin: can you confirm this actually fixes the issue with a non-
framework build, I don't know if I'll be able to test that before the
first 3.1a release.
--
resolution: ->
Changes by Ronald Oussoren :
--
status: pending -> closed
___
Python tracker
<http://bugs.python.org/issue4165>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Ronald Oussoren :
___
Python tracker
<http://bugs.python.org/issue4848>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/o
1901 - 2000 of 2445 matches
Mail list logo