Changes by Ezio Melotti ezio.melo...@gmail.com:
--
stage: - committed/rejected
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13465
___
___
Frank Wierzbicki fwierzbi...@gmail.com added the comment:
I have forked the devguide into http://hg.python.org/jython-docs/devguide/ --
this way I can merge changes from the main devguide as they make sense. DVCS
FTW :) -- I guess this issue can be closed.
--
Changes by Frank Wierzbicki fwierzbi...@gmail.com:
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13465
___
___
Frank Wierzbicki fwierzbi...@gmail.com added the comment:
I'll take a look at the dev guide this week and see how much it differs from
what I'd want to do and report back here. If it doesn't make sense to include a
Jython page here I can either copy content over or link to the CPython dev
Éric Araujo mer...@netwok.org added the comment:
python.org is not specific to CPython, but I agree with Antoine that
docs.python.org/devguide is. So I went and found the blog post that Frank
alludes to in the OP is here:
http://fwierzbicki.blogspot.com/2011/11/contributing-to-jython.html
Antoine Pitrou pit...@free.fr added the comment:
Hosting docs.python.org/devguide/jython doesn't seem like an
unreasonable idea at all to me, and what's the benefit to CPython in
making the Jython team go to the effort of building out independent
deployment and source control infrastructure
Ezio Melotti ezio.melo...@gmail.com added the comment:
I'd search the Jython devguide at http://www.jython.org/devguide/, having it at
http://docs.python.org/devguide/jython/ doesn't make much sense IMHO
(especially if it is a full guide with several pages).
--
New submission from Frank Wierzbicki fwierzbi...@gmail.com:
Nick suggested this as a comment on a blog post of mine -- I'll come up with
some content, but I wanted to log the bug straight away so I wouldn't forget.
--
components: Devguide
messages: 148200
nosy: brett.cannon,
Antoine Pitrou pit...@free.fr added the comment:
Uh, rather -1 on this. I would suggest Jython gets its own devguide (which can
of course copy stuff from CPython's), since Jython and CPython are distinct
projects. No need to confuse readers by mixing instructions for two different
projects in
Nick Coghlan ncogh...@gmail.com added the comment:
Hosting docs.python.org/devguide/jython doesn't seem like an unreasonable
idea at all to me, and what's the benefit to CPython in making the Jython team
go to the effort of building out independent deployment and source control
infrastructure
10 matches
Mail list logo