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
st
Ok, actually we are talking past each other. The problem Adam had apparently
has nothing to do with the migration or the pip stuff, it probably is just
caused by a bug introduced in a recent commit, the code Adam identified. We
should fix that once we have figured out all the details.
As far as
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 bra
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@python.org] On Behalf Of Brad
Friedm
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:
>
>
Hopefully to save someone a headache in the future:
Although I didn’t think it had anything to do with my problem, I was curious
why the ‘python setup.py build_ext’ command was failing with ‘[Error 5]: Access
is denied’. I put a ‘import ipdb; ipdb.set_trace()’ and found it’s because my
tools/n
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
Sorry for not being clear –
1) I’m not building on homebrew on mac :) I am building myself using VS2013.
2) Why do I need to use the setup.py? In any case, when I do this, ie running
‘python setup.py build_ext’ command, I get a [Error 5]: Access is denied. A
registry access failure perhaps? I
Sorry if this is duplicated… I’m not getting confirmation that my emails are
reaching the mailing list…
From: Adam Klein
Sent: Wednesday, June 04, 2014 10:18 AM
To: 'A list for users and developers of Python for .NET'
Subject: RE: [Python.NET] homebrew pythonnet, versus pip install --pre pythonne
Confirmed that commit
b65fa30c7b21cce263ed9ada982bd47bc18eea04 Use Assembly.Load(Byte[]) instead of
Assembly.LoadFrom.
leads to the behavior below for me ... and prior to that, things work. Any
suggestions would be welcome.
From: Adam Klein
Sent: Tuesday, June 03, 2014 7:23 PM
To: pythondotnet
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
12 matches
Mail list logo
