Differences between revisions 1 and 2
Revision 1 as of 2004-07-20 15:30:38
Size: 429
Comment:
Revision 2 as of 2004-07-20 16:12:54
Size: 1461
Editor: kansas
Comment: Added a some contrarian thoughts.
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:

----------

Importing a URL is a very bad idea. First, there are security issues, as you are executing code over which you don't have control. Also, you don't generally want libraries to be upgraded behind your back. The standard library gets upgraded, but a lot of work goes into keep that backward compatible -- in other libraries, this isn't the case. You want to make upgrades explicit in that case. Languages that have the ability to import URLs -- like PHP -- almost never use it.

A URL literal doesn't seem particularly useful. It would provide an alternative to, say, {{{url('http://something.com/whatever')}}} (e.g., {{{<http://something.com/whatever>}}}), but since URLs tend to be dynamic or configurable, a literal doesn't add significant value. However, a good URL class would be excellent, maybe a class that has an API similar to the [http://www.jorendorff.com/articles/python/path/ path] module. It would be great if both modules were builtins (or at least in the standard library).

-- IanBicking

Ideas

Design point: are syntax changes on the table, or not?

Add a basic URL type.

Import hook for importing from URLs (e.g. http://stdlib.python.org/2.3.4/pickle)


Importing a URL is a very bad idea. First, there are security issues, as you are executing code over which you don't have control. Also, you don't generally want libraries to be upgraded behind your back. The standard library gets upgraded, but a lot of work goes into keep that backward compatible -- in other libraries, this isn't the case. You want to make upgrades explicit in that case. Languages that have the ability to import URLs -- like PHP -- almost never use it.

A URL literal doesn't seem particularly useful. It would provide an alternative to, say, url('http://something.com/whatever') (e.g., <http://something.com/whatever>), but since URLs tend to be dynamic or configurable, a literal doesn't add significant value. However, a good URL class would be excellent, maybe a class that has an API similar to the [http://www.jorendorff.com/articles/python/path/ path] module. It would be great if both modules were builtins (or at least in the standard library).

-- IanBicking

What else?

References

Aaron Swartz's ideas: http://logicerror.com/webizingPython

TBL's original talk: http://www.w3.org/2002/Talks/0206-python/all.htm

Related: /F's idea for XML literals: http://effbot.org/zone/idea-xml-literal.htm

WebizingPython (last edited 2008-11-15 14:01:23 by localhost)

Unable to edit the page? See the FrontPage for instructions.