[Python.NET] homebrew pythonnet, versus pip install --pre pythonnet

Tony Roberts tony at pyxll.com
Thu Jun 5 00:44:56 CEST 2014

The projects/solutions still work the same as they did before, but I always
found the different targets a bit hit and miss as to how consistently they
were set up. Setup.py builds using msbuild and (more or less) the same
solution file that was there previously. You can still load it into visual
studio. Setup.py sets some build options according to the version of python
being used.

I suggested using setup.py as that's what I consider the most
reliable/reproducible method.

You don't need to build it in an IDE in order to embed python. You should
be able to just add a reference to the assembly built as part of the
setup.py build.

On Wednesday, June 4, 2014, Bradley Friedman <brad at fie.us> wrote:

> Yes.  But the problem is: before the migration, those things DID work.
>  And it was the pip/setup.py that needed to be fixed up.  It sounds like
> you’re saying you’ve sacrificed all of it just to get a pip install working
> for windows.  This is extremely troubling.  I have not looked at the git
> branch yet.  But now I need to investigate what exactly is going on.
> On Jun 4, 2014, at 1:46 PM, David Anthoff <anthoff at berkeley.edu
> <javascript:_e(%7B%7D,'cvml','anthoff at berkeley.edu');>> wrote:
> Pull requests to fix this are more than welcome :) I agree that building
> from the IDE should also work, but right now there doesn’t seem to be the
> man power to fix all of these things.
> *From:* PythonDotNet [
> mailto:pythondotnet-bounces+anthoff=berkeley.edu at python.org
> <javascript:_e(%7B%7D,'cvml','pythondotnet-bounces%2Banthoff%5Cx3dberkeley.edu at python.org');>
> ] *On Behalf Of *Brad Friedman
> *Sent:* Wednesday, June 4, 2014 9:49 AM
> *To:* A list for users and developers of Python for .NET
> *Subject:* Re: [Python.NET] homebrew pythonnet, versus pip install --pre
> pythonnet
> Umm. As an asside:  seriously?  You are only supporting setup.py builds
> from this branch?  That's a problem. Python.net <http://python.net/> is
> also used to embed python. Therefore, it should build from IDE on all
> platforms and also from an autotools system.
> On Jun 4, 2014, at 6:15 AM, Tony Roberts <tony at pyxll.com> wrote:
> Hi Adam,
> that 2.0.0.beta1 build was built from the source on github here:
> https://github.com/pythonnet/pythonnet
> You should build it using the setup.py script and not in the IDE.
> There are CI builds setup for both windows and linux (see README.md) if
> you want to see exactly how the wheel gets built.
> Best regards,
> Tony
> On Wed, Jun 4, 2014 at 3:48 AM, Bradley Friedman <brad at fie.us> wrote:
> Can you provide the contents of the ".Config" file that is built with your
> particular build solution?  There's a pretty good chance that the
> "FileNotFound" is actually mono trying to link back to Python shared
> libraries.  Though to be honest, debugging is going to be your best bet
> here.  You might try building in Xamarin or MonoDevelop on the mac, to be
> able to debug more easily.
> -brad
> On Jun 3, 2014, at 7:15 PM, Tribble, Brett <btribble at ea.com> wrote:
> _________________________________________________
> Python.NET <http://python.net/> mailing list - PythonDotNet at python.org
> <javascript:_e(%7B%7D,'cvml','PythonDotNet at python.org');>
> https://mail.python.org/mailman/listinfo/pythondotnet
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pythondotnet/attachments/20140604/62d767ca/attachment.html>

More information about the PythonDotNet mailing list