[Python-Dev] requirements for moving import over to importlib? (original) (raw)
Brett Cannon brett at python.org
Fri Feb 24 02:15:57 CET 2012
- Previous message: [Python-Dev] requirements for moving __import__ over to importlib?
- Next message: [Python-Dev] requirements for moving __import__ over to importlib?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I just tried this and I get a str/bytes issue. I also think your setup3k.py
command is missing build
and your build/scripts-3.2 is missing /hg
.
On Wed, Feb 22, 2012 at 19:26, Éric Araujo <merwok at netwok.org> wrote:
Hi Brett,
I think this message went unanswered, so here’s a late reply: Le 07/02/2012 23:21, Brett Cannon a écrit : > On Tue, Feb 7, 2012 at 15:28, Dirkjan Ochtman <dirkjan at ochtman.nl> wrote: >> [...] >> Anyway, I think there was enough of a python3 port for Mercurial (from >> various GSoC students) that you can probably run some of the very >> simple commands (like hg parents or hg id), which should be enough for >> your purposes, right? > > Possibly. Where is the code? # get Mercurial from a repo or tarball hg clone http://selenic.com/repo/hg/ cd hg # convert files in place (don’t commit after this :) python3.2 contrib/setup3k.py # the makefile is not py3k-aware, need to run manually # the current stable head fails with a TypeError for me PYTHONPATH=. python3.2 build/scripts-3.2 Cheers -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20120223/62ff6c98/attachment.html>
- Previous message: [Python-Dev] requirements for moving __import__ over to importlib?
- Next message: [Python-Dev] requirements for moving __import__ over to importlib?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]