A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2007-June/073671.html below:

[Python-Dev] [Python-3000] Python 3000 Status Update (Long!)

[Python-Dev] [Python-3000] Python 3000 Status Update (Long!) [Python-Dev] [Python-3000] Python 3000 Status Update (Long!)"Martin v. Löwis" martin at v.loewis.de
Tue Jun 19 22:53:09 CEST 2007
>> What would a registry of tranformation algorithms buy us compared to a
>> module with transformation functions?
> 
> Easier registering of custom transformations. Without a registry, you'd have
> to monkey-patch a module.

Or users would have to invoke the module directly.

I think a convention would be enough:

rot13.encode(foo)
rot13.decode(bar)

Then, "registration" would require to put the module on sys.path,
which it would for any other kind of registry as well.

My main objection to using an encoding is that for these,
the algorithm name will *always* be a string literal,
completely unlike "real" codecs, where the encoding name
often comes from the environment (either from the process
environment, or from some kind of input).

Regards,
Martin

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4