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/2008-March/078140.html below:

[Python-Dev] Proposal: from __future__ import unicode_string_literals

[Python-Dev] Proposal: from __future__ import unicode_string_literals [Python-Dev] Proposal: from __future__ import unicode_string_literalsLennart Regebro regebro at gmail.com
Mon Mar 24 12:38:55 CET 2008
On Mon, Mar 24, 2008 at 12:26 PM, "Martin v. Löwis" <martin at v.loewis.de> wrote:
>  http://svn.zope.org/zope.psycopgda/trunk/
>
>  Is that not the right source?

No, and yes. Many of the zope3 modules are installable as separate
modules. Zope 3 in general has been "eggified". This is not however
how everybody installs Zope3. Zope2 is not installed this way. Also,
most Zope2 products are not modules installed by setup.py.

>  To me "run against trunk" means that I check out some source, then
>  run "setup.py install" (or buildout, or make). This will invoke
>  2to3 behind the scenes.

I repeat: There is no setup.py install to run.

>  I guess I could better understand with a very specific example.
>  You gave Django as a very specific example, and I looked at Django,
>  and it works just fine with 2to3. "The Plone collective" is not
>  a specific example

It is a specific example.

-- 
Lennart Regebro: Zope and Plone consulting.
http://www.colliberty.com/
+33 661 58 14 64
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