Content-Type: multipart/alternative;
boundary="Apple-Mail=_1081C423-2100-4937-A026-8F3EA9460689"
--Apple-Mail=_1081C423-2100-4937-A026-8F3EA9460689
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=iso-8859-1
On 13 Jun, 2012, at 9:38, tanya wrote:
> Hello. I am just beginning with PyObjC, and so I downloaded =
XCode/PyObjC templates from =
http://svn.red-bean.com/pyobjc/trunk/pyobjc/pyobjc-xcode/ . Without =
changing anything I am running Instruments, and seeing that there are =
leaks in XCode 4.3 =
(https://dl.dropbox.com/u/16876271/Screen%20Shot%202012-06-13%20at%2011.22=
.26%20AM.png). I also downloaded other templates based on that =
(https://github.com/gregneagle/Xcode4CocoaPythonTemplates), and these =
also leak. What can I do to resolve this? Is it too minor to worry =
about?
I don't use the Xcode templates myself (I'm an command-line nerd and use =
vim and py2app instead). The leaks are probably not relevant, what does =
Xcode say about the source of these leaks? If you select the leak =
Instruments should tell you where the memory was allocated, and that =
might tell us what's going on here.
Ronald
>=20
> Thanks for your help!
>=20
> -t
> =
--------------------------------------------------------------------------=
----
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and=20
> threat landscape has changed and how IT managers can respond. =
Discussions=20
> will include endpoint security, mobile security and the latest in =
malware=20
> threats. =
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_________________=
______________________________
> Pyobjc-dev mailing list
> Pyobjc-dev@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev
--Apple-Mail=_1081C423-2100-4937-A026-8F3EA9460689
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=iso-8859-1

I =
don't use the Xcode templates myself (I'm an command-line nerd and use =
vim and py2app instead). The leaks are probably not relevant, what =
does Xcode say about the source of these leaks? If you select the leak =
Instruments should tell you where the memory was allocated, and that =
might tell us what's going on =
here.