Closed ivirshup closed 5 years ago
Yes, this was caused by yesterday's PR from someone else. I had tested it only on python3. I'll change the python version in the shebang and also this particular line.
This brings up this whole annoying python3 unicode issue. I try to avoid unicode strings as they're slower, but here it looks like I have to use it. I've tested it now and it seems to work, but may look one day into the unnecessary use of utf8 here.
On Wed, Oct 3, 2018 at 12:15 PM Maximilian Haeussler maximilianh@gmail.com wrote:
Yes, this was caused by yesterday's PR from someone else. I had tested it only on python3. I'll change the python version in the shebang and also this particular line.
Thanks for bringing this up!
On Wed, Oct 3, 2018 at 1:23 PM Maximilian Haeussler maximilianh@gmail.com wrote:
This brings up this whole annoying python3 unicode issue. I try to avoid unicode strings as they're slower, but here it looks like I have to use it. I've tested it now and it seems to work, but may look one day into the unnecessary use of utf8 here.
On Wed, Oct 3, 2018 at 12:15 PM Maximilian Haeussler < maximilianh@gmail.com> wrote:
Yes, this was caused by yesterday's PR from someone else. I had tested it only on python3. I'll change the python version in the shebang and also this particular line.
Also, I cannot see any shebang lines anymore, even for yesterday's master branch, that specify python2. I wonder if you could do another git pull. In the master branch, it should all be just "python" now.
On Wed, Oct 3, 2018 at 1:23 PM Maximilian Haeussler maximilianh@gmail.com wrote:
Thanks for bringing this up!
On Wed, Oct 3, 2018 at 1:23 PM Maximilian Haeussler maximilianh@gmail.com wrote:
This brings up this whole annoying python3 unicode issue. I try to avoid unicode strings as they're slower, but here it looks like I have to use it. I've tested it now and it seems to work, but may look one day into the unnecessary use of utf8 here.
On Wed, Oct 3, 2018 at 12:15 PM Maximilian Haeussler < maximilianh@gmail.com> wrote:
Yes, this was caused by yesterday's PR from someone else. I had tested it only on python3. I'll change the python version in the shebang and also this particular line.
You're totally right, I must have been looking at cellbrowser.py
on ace4d882f9. In general though, homebrew sets a symlink for python->python3
, so that's probably why python2 was being used for me.
I certainly strive to make at least cbBuild work with both python2 and python3, so thanks for opening this ticket. I'm closing it now as the issue is hopefully solved. Let me know if you run into any other issues.
Good to know about homebrew having python3 as the default. ArchLinux is the same, most other linux distros will keep python2 as the default for a while.
On Thu, Oct 4, 2018 at 2:18 AM Isaac Virshup notifications@github.com wrote:
You're totally right, I must have been looking at cellbrowser.py on ace4d88 https://github.com/maximilianh/cellBrowser/commit/ace4d882f99bb6034219bc75f9230141741d3b3e. In general though, homebrew sets a symlink for python->python3, so that's probably why python2 was being used for me.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/maximilianh/cellBrowser/issues/40#issuecomment-426844845, or mute the thread https://github.com/notifications/unsubscribe-auth/AAS-TSsjCpLULTVOXBmdhQQWwVK1Wmspks5uhVPLgaJpZM4XFYQX .
Similar to #35, running the example build command throws an error. Here's the traceback:
From what I can tell, this is caused by having the shebang of
cbBuild
call forpython2
to be used and the usage ofencoding
as an argument tosubprocess.Popen
, as introduced by #36. In mypython v2.7.15
installation,subprocess.Popen
does not have anencoding
argument:I can get around this error by using: