I summarize some discussions about the name we had on IRC:

At first, @xcombelle liked PyTcLBridge

@dereckson noted some OS/distros like to add py- prefixes, and so that could be confusing. About packaging, some linux distros don't comply really well with CamelCase (FreeBSD does). @mst on Freenode TCL jokes about this: "tcl-py-py-tcl-py-bridge.rpm"

@xcombelle stressed the project name must convey the idea of their role, and not be arbitrary.

Freenode TCL channel notes py2tcl would be simple or pytcl, the last already being taken on GitHub as an user account (thanks to kyak and dbohdan for their feedback).

Current suggestions

When @dereckson noticed we could extend it to other languages in the future, @xcombelle suggests:

• cuppergate / coppergate (too many results)
• dynbridge (to open to other dynamic languages)

As such, « dynbridge » seems to be the most promising name, we can adopt it as codename, and change it later or adopt it as product name.

Created Dynbridge project.