@filmor @vmuriart @tonyroberts please review documentation update. The motivation was outdated information on python guide referencing these docs:

https://github.com/kennethreitz/python-guide/pull/746

👍

Just one small thing: Do we really want people to use npython? Does that make sense at all, seeing that it's completely equivalent to running python and then importing clr?

@filmor npython is still useful for quickly troubleshooting the embedding cases:

https://github.com/pythonnet/pythonnet/search?q=npython&type=Issues

Also @cgohlke still bundles npython.exe in his wheels:

http://www.lfd.uci.edu/~gohlke/pythonlibs/#pythonnet

@denfromufa I agree with @filmor that it's better for new users to be pointed to the regular python instead of nPython, otherwise they might get the impression somehow using pythonnet requires npython. What about changing it to python, and adding a note that nPython is available as an example of embedding the CPython interpreter in a c# application?

Agreed! Let me change the purpose of nPython.exe in these docs from "using
pythonnet" to "example of embedding Python in .NET". The primary way to use
pythonnet should be "import clr" in python/ipython interpreter.

On Tue, Sep 13, 2016 at 10:03 AM, Tony Roberts [email protected]
wrote:

@denfromufa https://github.com/denfromufa I agree with @filmor
https://github.com/filmor that it's better for new users to be pointed
to the regular python instead of nPython, otherwise they might get the
impression somehow using pythonnet requires npython. What about
changing it to python, and adding a note that nPython is available as an
example of embedding the CPython interpreter in a c# application?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#5 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHgZ5S9gdlOhAIFP7-NIc2HlVDtTG-vPks5qprtJgaJpZM4J7QJD
.

@tonyroberts @filmor done! please go through a second round of review.

Looks good to me.

me too

Then squash and merge :)

I started working on draft release notes. Let's mark all issues to be
resolved for this release.

On Wed, Sep 14, 2016 at 10:08 AM, Benedikt Reinartz <
[email protected]> wrote:

Merged #5 #5.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#5 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHgZ5VVqMSjOPnkZIrnxV1JrkSuyRiCxks5qqA3ugaJpZM4J7QJD
.