[Python-checkins] python/dist/src/Python import.c,2.175.2.2,2.175.2.3
Guido van Rossum
guido@python.org
Sun, 02 Jun 2002 09:01:32 -0400
- Previous message: [Python-checkins] python/dist/src/Python
import.c,2.175.2.2,2.175.2.3
- Next message: [Python-checkins] python/dist/src/Lib CGIHTTPServer.py,1.24,1.25 compileall.py,1.11,1.12 dircache.py,1.10,1.11 dospath.py,1.28,1.29 filecmp.py,1.11,1.12 imputil.py,1.24,1.25 linecache.py,1.10,1.11 macpath.py,1.38,1.39 mhlib.py,1.31,1.32 ntpath.py,1.48,1.49 os2emxpath.py,1.5,1.6 posixpath.py,1.49,1.50 pstats.py,1.25,1.26 py_compile.py,1.20,1.21 pydoc.py,1.64,1.65 statcache.py,1.15,1.16 uu.py,1.18,1.19 zipfile.py,1.22,1.23
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
> > > + PySys_WriteStderr(
> > > + "# code too large: can't write %s\n",
> > > + cpathname);
> >
> > Maybe this should be a call to PyErr_Warn instead?
>
> That's fine with me. But I'm not sure the warning will be helpful.
> Any suggestions for wording? Is what's there good enough?
>
> Here's my suggestion:
>
> PyOS_snprintf(buffer, sizeof(buffer),
> "code too large: can't write %.80s\n",
> cpathname);
> PyErr_Warn(PyExc_RuntimeWarning, buffer);
I take it back. All warnings with writing pyc files are reported in
this fashion (i.e., a message is printed only in verbose mode).
--Guido van Rossum (home page: http://www.python.org/~guido/)
- Previous message: [Python-checkins] python/dist/src/Python
import.c,2.175.2.2,2.175.2.3
- Next message: [Python-checkins] python/dist/src/Lib CGIHTTPServer.py,1.24,1.25 compileall.py,1.11,1.12 dircache.py,1.10,1.11 dospath.py,1.28,1.29 filecmp.py,1.11,1.12 imputil.py,1.24,1.25 linecache.py,1.10,1.11 macpath.py,1.38,1.39 mhlib.py,1.31,1.32 ntpath.py,1.48,1.49 os2emxpath.py,1.5,1.6 posixpath.py,1.49,1.50 pstats.py,1.25,1.26 py_compile.py,1.20,1.21 pydoc.py,1.64,1.65 statcache.py,1.15,1.16 uu.py,1.18,1.19 zipfile.py,1.22,1.23
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]