On Tue, Sep 9, 2014 at 4:03 AM, Jean-Baptiste Lab
jeanbaptiste@gmail.com wrote:
Or wouldn't it be enough to simply mandate that exists() return something
that can be tested against True/False?
If that's the case, wouldn't a bit of wrapping around and implementing the
__eq__/__neq__
On Mon, Sep 8, 2014 at 10:24 PM, William Blevins wblevins...@gmail.com
wrote:
This might be obvious, but it the exception pattern not popular in python?
Sure, but we don't want everyone testing for tool existence to have to wrap
that in an exception handler.
--
Gary
To test against True/False one should better implement __nonzero__, not
__eq__ or something :-) That way one could then use the form if obj:, not
an ugly form of if obj == True:.
Thanks,
Vasily
09 сент. 2014 г. 12:03 пользователь Jean-Baptiste Lab
jeanbaptiste@gmail.com написал:
Or
On 9 September 2014 11:56, Gary Oberbrunner ga...@oberbrunner.com wrote:
On Tue, Sep 9, 2014 at 4:03 AM, Jean-Baptiste Lab
jeanbaptiste@gmail.com wrote:
Or wouldn't it be enough to simply mandate that exists() return something
that can be tested against True/False?
If that's the case,
What are your thoughts on infra to help provide a common mean to find tools for
different platforms.
I believe what I have in Parts for this work pretty well. It allow an
extensible and generally easy way for one to define how to find a given tool
version(s) for a some combination of host and
On Tue, Sep 9, 2014 at 11:08 AM, Kenny, Jason L jason.l.ke...@intel.com
wrote:
What are your thoughts on infra to help provide a common mean to find
tools for different platforms.
I believe what I have in Parts for this work pretty well. It allow an
extensible and generally easy way for
I think you are missing the point or maybe I am.
Given the tool revamp.
How will we support:
1) Cross-builds.
a. I want to build 32-bit and 64- at the same time
b. I want to build for android arm and x86
2) Selecting different versions of gcc?
3) How do I iterate
On Tue, Sep 9, 2014 at 12:03 PM, Kenny, Jason L jason.l.ke...@intel.com
wrote:
I think you are missing the point or maybe I am.
Given the tool revamp.
How will we support:
1) Cross-builds.
a. I want to build 32-bit and 64- at the same time
b. I want to build for
For reference sake I added /etc/paths and /etc/path.d/* to the path since
it was claimed that Apple sanctioned it as the way to add paths to the
system and is used by Xquartz installation to add /opt/X11/bin to the
path. On my system it also catches the TexLive installation paths
/usr/texbin
Thanks Gary for your thoughts!
I have a few thought about the response. But I think I would start off with
just one item.
When you look at what you have suggested, we have a cross build you suggest
something to what I would think..
env1=Environment(tools=['intelc_32_arm', ...])
What is wrong
On Tue, Sep 9, 2014 at 2:07 PM, Kenny, Jason L jason.l.ke...@intel.com
wrote:
Thanks Gary for your thoughts!
I have a few thought about the response. But I think I would start off
with just one item.
When you look at what you have suggested, we have a cross build you
suggest something
11 matches
Mail list logo
