t for users and developers of Python for .NET
Subject: Re: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet
Agreed - had no problem building in VS. I did have some problems in setup.py,
that I pointed out (but only having to do with my registry keys not aligning
with what the script
is mind blowing. Kudos once again.
From: PythonDotNet [mailto:pythondotnet-bounces+aklein=bmcm@python.org] On
Behalf Of David Anthoff
Sent: Wednesday, June 04, 2014 3:38 PM
To: 'A list for users and developers of Python for .NET'
Subject: Re: [Python.NET] homebrew pythonnet, versus pi
riedman
> *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
> f
Bradley Friedman
Sent: Wednesday, June 4, 2014 11:36 AM
To: pythondotnet@python.org
Subject: Re: [Python.NET] homebrew pythonnet, versus pip install --pre
pythonnet
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
ix all of these things.
>
> From: PythonDotNet
> [mailto:pythondotnet-bounces+anthoff=berkeley@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
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 pr
Umm. As an asside: seriously? You are only supporting setup.py builds from
this branch? That's a problem. 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 wrote:
>
>
n…)
From: Adam Klein
Sent: Wednesday, June 04, 2014 8:55 AM
To: A list for users and developers of Python for .NET
Subject: RE: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet
Sorry for not being clear –
1) I’m not building on homebrew on mac :) I am building myself using
Right, so the assembly is indeed found in the pythonpath, but other assemblies
it depends on transitively (in the same directory) are not loaded as a result
of the malformation of the path + name string ...
On Jun 3, 2014, at 7:48 PM, "Tribble, Brett"
mailto:btrib...@ea.com>> wrote:
It has bee
irm
others see this behavior as well.
From: PythonDotNet [mailto:pythondotnet-bounces+aklein=bmcm@python.org] On
Behalf Of Tony Roberts
Sent: Wednesday, June 04, 2014 6:15 AM
To: A list for users and developers of Python for .NET
Subject: Re: [Python.NET] homebrew pythonnet, versus pip install
: pythondotnet@python.org
Subject: RE: [Python.NET] homebrew pythonnet, versus pip install --pre pythonnet
I think I found one problem ... in FindAssembly (in assemblymanager.cs), the
name it passes for assembly dependencies seems to be of the following form:
"c:\\path\\Assembly, Version=2.0.0.0, Cu
I think I found one problem ... in FindAssembly (in assemblymanager.cs), the
name it passes for assembly dependencies seems to be of the following form:
"c:\\path\\Assembly, Version=2.0.0.0, Culture=neutral, PublicKeyToken=null"
It therefore fails to find the assembly...
From: PythonDotNet [m
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 bu
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 mig
It has been a while since I've had to deal with this, but make sure that your
assembly is in the system path and/or pythonpath if it is not registered in the
GAC.
From: PythonDotNet [mailto:pythondotnet-bounces+btribble=ea@python.org] On
Behalf Of Adam Klein
Sent: Tuesday, June 03, 2014 4:0
15 matches
Mail list logo
