Martin v. Löwis mar...@v.loewis.de added the comment:
All active branches use this now.
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1303434
___
Martin v. Löwis mar...@v.loewis.de added the comment:
Thanks for the patch, committed as r84487. I'll try it out with the next 3.2
alpha release.
Leaving this open for possible backports.
--
___
Python tracker rep...@bugs.python.org
Changes by Martin v. Löwis mar...@v.loewis.de:
--
resolution: - accepted
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1303434
___
___
Daniel Stutzbach dan...@stutzbachenterprises.com added the comment:
Attached is a slightly improved patch. It cleans up some whitespace issues
with James's patch and filters out *_d.pdb files if they exist. I tested it on
my system and it correctly produces a .zip file containing the .pdb
Changes by Mark Lawrence breamore...@yahoo.co.uk:
--
stage: - patch review
versions: +Python 3.2 -Python 2.7, Python 3.0
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1303434
___
James Lee j...@jbit.net added the comment:
Attached is a simple patch against msi.py from the py3k branch. It generates a
.zip file containing all the PDB files (minus a select few) in the PCbuild
directory. I imagine most people only want python31.pdb, but it is very
frustrating when you
James Lee j...@jbit.net added the comment:
Right now if you have any moderately complex Python based application (or
extension set) the only way to easily debug it on windows is by building Python
yourself, which is a horrible solution since it means you may end up with a
subtly different
Martin v. Löwis mar...@v.loewis.de added the comment:
While including the PDB in the MSI distribution
would require a patch (and might not be the best solution since 99%
of people won't need it), copying the PDB to some place does not
This is not the case. I'm not at all clear what specific
James Lee j...@jbit.net added the comment:
Ah, sorry, I see what you mean now... I thought the request for patch was to
modify the installer itself, but it meant just make the msi.py script generate
a separate zip file alongside the .msi installer.
I'll take a look at providing a patch with
Chris Grebeldinger cgreb...@gmail.com added the comment:
Hi Martin,
As an aside to the request, is the pdb for the python dll currently available
anywhere?
--
nosy: +cgrebeld
___
Python tracker rep...@bugs.python.org
Martin v. Löwis mar...@v.loewis.de added the comment:
As an aside to the request, is the pdb for the python dll currently
available anywhere?
Only on my hard disk, and then only for the very last release. The
status of the issue is the same as in 2006: without patches, nothing
will happen.
Marc-Andre Lemburg m...@egenix.com added the comment:
Hi Martin, wouldn't just uploading the pythonXX.pdb to the release page
be enough.
The distributed DLL already points to the source location on your system
:-) E.g. for Python 2.5, this was c:\loewis\25\python\PCbuild\python25.pdb
Or are
Changes by Marc-Andre Lemburg m...@egenix.com:
--
versions: +Python 2.7, Python 3.0
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1303434
___
___
Martin v. Löwis mar...@v.loewis.de added the comment:
Hi Martin, wouldn't just uploading the pythonXX.pdb to the release page
be enough.
It's not clear to me what is being requested: just that single PDB file,
or also the PDB files for all of the extension modules? Also, shouldn't
the file be
Marc-Andre Lemburg m...@egenix.com added the comment:
On 2009-02-11 22:20, Martin v. Löwis wrote:
Martin v. Löwis mar...@v.loewis.de added the comment:
Hi Martin, wouldn't just uploading the pythonXX.pdb to the release page
be enough.
It's not clear to me what is being requested: just
Changes by Daniel Stutzbach dan...@stutzbachenterprises.com:
--
nosy: +stutzbach
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1303434
___
___
16 matches
Mail list logo
