[issue5819] Add PYTHONPREFIXES environment variable
Ian Bicking added the comment: Also with respect to the patch, for consistency there needs to be changes to distutils to make use of this variable. PYTHONUSERBASE included changes so that you can install based on that variable. -- ___ Python tracker <http://bugs.python.org/issue5819> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5819] Add PYTHONPREFIXES environment variable
Ian Bicking added the comment: This has a similar purpose to virtualenv, but using an environmental variable. An earlier package, workingenv, also used an environmental variable, and this led to a set of problems. The biggest problem is that the environmental variable is inherited by subprocesses. This means if you install hg globally, then do subprocess.call(['hg', ...]), then hg will have picked up your local environment. Sometimes this is what you want (e.g., when using ipython) and sometimes not (probably not when using hg). Another problem is that scripts aren't really sticky with respect to the environment. When you install a script using this, it may only work when that same environmental variable is set. But the script remains present and callable regardless. Also, it's hard to mix and match environments in this system. These are real-world problems I encountered with workingenv, and virtualenv has resolved them very reliably by instead using sys.executable to select the environment. This requires some infrastructure in each environment which is unfortunate, but the result is more consistent behavior. -- nosy: +ianb ___ Python tracker <http://bugs.python.org/issue5819> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4330] wsgiref.validate doesn't accept arguments to readline
Ian Bicking <[EMAIL PROTECTED]> added the comment: cgi started using this argument due to the potential of a DoS attack without the length limit. So undoing this in cgi (even as an option) would be a regression. ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4330> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4330] wsgiref.validate doesn't accept arguments to readline
Ian Bicking <[EMAIL PROTECTED]> added the comment: Yes, and I've wanted to deprecate paste.lint, but I can't because people use it over wsgiref.validate because it had this change applied. Yes, cgi.FieldStorage changed, but now that it's changed wsgiref needs to be compatible with it to be viable. Mostly the WSGI spec has been wrong on this for some time, but we've never gone through the process of updating it (though it has been brought up several times on Web-SIG). ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4330> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4330] wsgiref.validate doesn't accept arguments to readline
Ian Bicking <[EMAIL PROTECTED]> added the comment: This renders wsgiref.validate.validator completely useless, because it cannot be used with any existing code. ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4330> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4330] wsgiref.validate doesn't accept arguments to readline
New submission from Ian Bicking <[EMAIL PROTECTED]>: The method wsgiref.validate:InputWrapper.readline doesn't take any arguments. It should take an optional size argument. Though this isn't part of the WSGI specification, the cgi module uses this argument when parsing the body, and in practice no applications that use cgi.FieldStorage (which is most applications) are compatible with wsgiref.validate as a result. Simply adding a *args that is passed to the underlying file fixes this. -- components: Library (Lib) messages: 75920 nosy: ianb severity: normal status: open title: wsgiref.validate doesn't accept arguments to readline versions: Python 2.6 ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4330> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4056] :Class: causes exception
New submission from Ian Bicking <[EMAIL PROTECTED]>:
I used a reference like :Class:`something` (note the capitalization) and
got this exception:
Traceback (most recent call last):
File
"/home/ianb/src/env/lib/python2.4/site-packages/sphinx/__init__.py",
line 135, in main
app.builder.build_update()
File
"/home/ianb/src/env/lib/python2.4/site-packages/sphinx/builder.py", line
201, in build_update
summary='targets for %d source files that are '
File
"/home/ianb/src/env/lib/python2.4/site-packages/sphinx/builder.py", line
241, in build
self.write(docnames, updated_docnames, method)
File
"/home/ianb/src/env/lib/python2.4/site-packages/sphinx/builder.py", line
276, in write
doctree = self.env.get_and_resolve_doctree(docname, self)
File
"/home/ianb/src/env/lib/python2.4/site-packages/sphinx/environment.py",
line 779, in get_and_resolve_doctree
self.resolve_references(doctree, docname, builder)
File
"/home/ianb/src/env/lib/python2.4/site-packages/sphinx/environment.py",
line 998, in resolve_references
raise RuntimeError('unknown xfileref node encountered: %s' % node)
RuntimeError: unknown xfileref node encountered: deliverance.rules.Drop
--
assignee: georg.brandl
components: Documentation tools (Sphinx)
messages: 74385
nosy: georg.brandl, ianb
severity: normal
status: open
title: :Class: causes exception
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue4056>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3037] in output
Ian Bicking <[EMAIL PROTECTED]> added the comment: Armin says this is a bug that has now been resolved in Jinja ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3037> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3037] in output
Ian Bicking <[EMAIL PROTECTED]> added the comment: You can see the source that produces this in http://svn.pythonpaste.org/Paste/trunk at revision 7387 ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3037> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3037] in output
New submission from Ian Bicking <[EMAIL PROTECTED]>: I updated to sphinx trunk and made just a few small changes in my template, and I'm now seeing: Note specifically "", which comes right before extrahead. -- assignee: georg.brandl components: Documentation tools (Sphinx) messages: 67696 nosy: georg.brandl, ianb severity: normal status: open title: in output type: behavior ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3037> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
