GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • [ date ]
  • [ thread ]
  • [ subject ]
  • [ author ]

This view

  • Original page
  • New address

GeezerVison is showing mail.python.org — [Python-Dev] [Python-3000] PyString -> PyBytes C API renaming

[Python-Dev] [Python-3000] PyString -> PyBytes C API renaming

Stefan Behnel stefan_ml at behnel.de
Thu May 29 12:28:21 CEST 2008

  • Previous message: [Python-Dev] [Python-3000] PyString -> PyBytes C API renaming
  • Next message: [Python-Dev] [Python-3000] PyString -> PyBytes C API renaming
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Nick Coghlan wrote:
> Stefan Behnel wrote:
>> Besides, how likely is it that users set a breakpoint on the
>> PyBytes/PyString functions?
> 
> Not very likely at all - but it would still be nice if the PyBytes_*
> symbols were visible to the linker as well as the preprocessor.

Right, that's a nice-to-have, an add-on. Why don't we just let Christian
finish his work, which is vital for the beta release? Then it's still time to
file a bug report on the missing bits and provide a patch that adds linker
symbols for PyBytes_*() in Py2.6 as an additional feature.

Stefan


  • Previous message: [Python-Dev] [Python-3000] PyString -> PyBytes C API renaming
  • Next message: [Python-Dev] [Python-3000] PyString -> PyBytes C API renaming
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the Python-Dev mailing list
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.