[Python-Dev] Python 2.0b2 note for Windows developers
Barry Scott
barry at scottb.demon.co.uk
Sat Oct 14 19:28:45 EDT 2000
More information about the Python-list mailing list
Sat Oct 14 19:28:45 EDT 2000
- Previous message (by thread): [Python-Dev] Python 2.0b2 note for Windows developers
- Next message (by thread): [Python-Dev] Python 2.0b2 note for Windows developers
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> -----Original Message----- > From: Tim Peters [mailto:tim_one at email.msn.com] > Sent: 08 October 2000 20:29 > To: Barry Scott; PythonDev; Python list > Subject: RE: [Python-Dev] Python 2.0b2 note for Windows developers > > > [Barry] > > Two requests: > > > > 1. Can you ship the .PDB files for the debug images so devo's > > do not need to build the python sources to debug extensions. > > And Yes I know the .ZIP will be huge. If you want a > > compromise only include the .PDB for python20_d.dll. > > Sure! Most .pdb files are highly compressible, and the zip size hit isn't > anything to worry about. Thanks > > > 2. Place the files into libs, pyd etc dirs. I had to extract > > the groups into the right places which is a bit tedious > > and error prone. > > No. If you want a directory structure that doesn't match the actual build > directory structure, I can't read your mind, and have no reason to believe > that the specific artificial structure you have in mind is of use to anyone The structure I refer to is the one used by the Python Windows installer. > but you. Don't be so helpless <wink>: write a tiny Python script to move I comment not because I'm lazy but because it seemed that every developer would need to reorganise the files. > the files where you want them after unpacking. What I upload will be an > exact image of the build directory structure. Most feedback I've gotten is > that people want exactly that, because they *want* to compile Python I'd not thought of that. MY assumption was that I build the release windows code against the files installed by the python windows installer. And that the debug settings would logically point into the same structure. > themselves and just want to avoid jumping thru all the snaky hoops needed to > compile the 3rd-party subprojects (from _tkinter to zlib). > > alphabetically y'rs - tim Barry
- Previous message (by thread): [Python-Dev] Python 2.0b2 note for Windows developers
- Next message (by thread): [Python-Dev] Python 2.0b2 note for Windows developers
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list