<sb0>
whitequark, what is the conda version on win7-buildbot? the tests are broken there but work fine when run manually (with a recent conda, that the packages now require)
<GitHub46>
[artiq] jordens commented on issue #738: Yes. The drawback is that it doesn't work anymore. If sensitivity is the problem, then getting rid of the version check entirely would be the answer.... https://github.com/m-labs/artiq/issues/738#issuecomment-306428529
<rjo>
sb0: then those examples should get more annotation mentioning their non-functioning status and that plan.
<GitHub90>
[artiq] sbourdeauducq commented on issue #736: It's quite simple, in Python you can do integer operations on booleans directly, with ``True`` implicitly converted to 1 and ``False`` implicitly converted to 0, e.g.:... https://github.com/m-labs/artiq/issues/736#issuecomment-306431631
<GitHub186>
[artiq] sbourdeauducq commented on issue #736: Also it's harsh of you to say that compiler issues are "systematically" delayed; look at the commit log for April 22 to see some counter-examples. https://github.com/m-labs/artiq/issues/736#issuecomment-306438592
<GitHub16>
[artiq] sbourdeauducq commented on issue #665: fastentrypoints breaks the new-style conda noarch package (and the old style noarch breaks entry points on Windows with recent conda, resulting in a "Failed to create process" error).... https://github.com/m-labs/artiq/issues/665#issuecomment-306440292
<GitHub134>
[artiq] jordens commented on issue #736: I didn't say that! That was a policy question, not a blanket statement about the past. To me a compiler where I don't have to worry that much about hitting and then circumnavigating unexpectedly buggy or slow behavior is at the top of my wishlist. Let me rephrase it: How important are compiler bugs to people and can we ignore them for now if there are workarounds? https://github.com/m-labs/artiq/issues
<GitHub18>
[artiq] sbourdeauducq commented on issue #738: We were already removing ``.dirty`` because it generates a lot of noise (have a few uncommitted modifications laying around, and it triggers). https://github.com/m-labs/artiq/issues/738#issuecomment-306489103
rohitksingh has joined #m-labs
<GitHub102>
[artiq] jordens commented on issue #738: I honestly prefer that noise over having to (and forgetting to) walk each user and myself through `git status`/`git diff` just to be sure that there are not "a few uncommitted modifications lying around".... https://github.com/m-labs/artiq/issues/738#issuecomment-306493944
<GitHub153>
[artiq] dhslichter commented on issue #736: I am with @cjbe, things like #407, #685, and also #719 are probably of more importance to our day-to-day usage. I don't use booleans as integers, at least not in the way that @jordens is describing in the initial post. I think there is a balance to be struck between allowing for all the things Python does in ARTIQ Python, and making things too restrictive in ARTIQ Python, but this seems like a fairly
<GitHub92>
[artiq] dhslichter commented on issue #736: I am with @cjbe, things like #407, #685, and also #719 are more importanct to our day-to-day usage. I don't use booleans as integers, at least not in the way that @jordens is describing in the initial post. I think there is a balance to be struck between allowing for all the things Python does in ARTIQ Python, and making things too restrictive in ARTIQ Python, but this seems like a fairly simple thing f
<GitHub162>
[artiq] dhslichter commented on issue #736: I am with @cjbe, things like #407, #685, and also #719 are more important to our day-to-day usage. I don't use booleans as integers, at least not in the way that @jordens is describing in the initial post. I think there is a balance to be struck between allowing for all the things Python does in ARTIQ Python, and making things too restrictive in ARTIQ Python, but this seems like a fairly simple thing
jboulder has joined #m-labs
<GitHub192>
[artiq] r-srinivas commented on issue #736: I think the only time we've hit this is at some point we were setting up some chip selects with ttls and I think `ttl.set_o(1)` throws an error? Of course, one can work around this fairly easily. https://github.com/m-labs/artiq/issues/736#issuecomment-306528912
<GitHub44>
[artiq] sbourdeauducq commented on issue #739: For maximum obnoxiousness, the 9-character bug only appears when the conda package is built by the buildbot, when doing a local conda build it has the correct 8 characters. https://github.com/m-labs/artiq/issues/739#issuecomment-306567382