Re: [Python-Dev] py34 makes it harder to read all of a pty
On Thu, Nov 13, 2014 at 6:34 PM, Charles-François Natali wrote: > 2014-11-12 22:16 GMT+00:00 Buck Golemon : >> This is due to the fix for issue21090, which aimed to un-silence errors >> which previously went unheard. The fix is for me, as a user, to write a loop >> that uses os.read and interpretes EIO as EOF. This is what I had hoped >> file.read() would do for me, however, and what it used to do in previous >> pythons. > > > There's no reason for read() to interpret EIO as EOF in the general > case: it was masked in previous versions because of a mere bug. The > behavior is now correct, although being able to retrieve the data read > so far in case of a buffered read could be useful. Every change breaks someone's workflow. http://xkcd.com/1172/ ChrisA ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Who's using VS/Windows to work on Python?
Just wondering who is regularly/occasionally using VS 2010 to work on Python? Also, who currently owns the Windows buildbots and are you willing/able to add a VS 2015 Preview installation (or give me access so I can do it)? I can also set up a VS 2015 buildbot, but the old ones will break if the projects change (I should do this anyway to at least become familiar with how the buildbots work...) I want to get a feel for who will be disrupted when I merge in the changes to build with VS 2015, which will help influence when that merge occurs. VS 2015 Preview was just released yesterday, and while it's not perfect yet, it's isolated enough from VS 2010 that there won't be any issues installing them both (I can't say the same for VS 2013...). If people are okay with this, then we can consider merging the changes sooner. Once VS 2015 RC is released, I'll be looking to merge asap., but I don't see a strong need to do it before then other than a longer bake time. (In any case, the old project files will still be there, but right now it's easier to handle when those change. Once they are in their own directory, changes to the VS 2010 projects will need to be duplicated by hand in the VS 2015 projects, and while the converse is true, it's not as critical.) Cheers, Steve ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Who's using VS/Windows to work on Python?
On 13/11/2014 19:47, Steve Dower wrote: Just wondering who is regularly/occasionally using VS 2010 to work on Python? I use VS 2010 (and VS 2008 if I'm building 2.7). Frankly my time has been so scarce this last year, I don't manage to use them from one month to the next. But I do use them. I want to get a feel for who will be disrupted when I merge in the changes to build with VS 2015, which will help influence when that merge occurs. VS 2015 Preview was just released yesterday, and while it’s not perfect yet, it’s isolated enough from VS 2010 that there won’t be any issues installing them both (I can’t say the same for VS 2013…). If people are okay with this, then we can consider merging the changes sooner. Once VS 2015 RC is released, I’ll be looking to merge asap., but I don’t see a strong need to do it before then other than a longer bake time. Are the changes for VS2015 likely to hamper a build against VS2010? TJG ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Who's using VS/Windows to work on Python?
On 11/13/2014 11:47 AM, Steve Dower wrote: > > Just wondering who is regularly/occasionally using VS 2010 to work on Python? Very occasional. In fact, my MSDS subscription expired and I missed the last call for renewals. :( If it will help (and I can get a renewed subscription), I can built/test on my Win7 machine. -- ~Ethan~ ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Who's using VS/Windows to work on Python?
Tim Golden wrote: > Are the changes for VS2015 likely to hamper a build against VS2010? I hadn't tried it, but it looks like it works fine with VS2010 (with a few extra warnings, but nothing fatal as far as the build is concerned). I'm a little surprised, tbh, but not overly upset :) Guess I can go ahead and start merging the changes (via issues w/patches) whenever I like then. The most painful change will probably be moving the x86 outputs from PCBuild to PCBuild\win32, but I'll get that into the buildbot scripts and it should be fine. Cheers, Steve ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Who's using VS/Windows to work on Python?
Steve Dower writes: > Also, who currently owns the Windows buildbots and are you > willing/able to add a VS 2015 Preview installation (or give me > access so I can do it)? (...) I've got several of the Windows buildbots, and could add this. Is there benefit to just starting with one (I've got XP, Win7 and Win8) first to save some time? My only real concern is to verify that this will co-exist properly with the existing VS installations and buildbot build process. I note that the download page says not to use on production computers. That's probably just a CYA, and I don't mind if VS itself has issues, but if it risks compromising other aspects of the buildbot, then I think testing on a different machine would be preferred. Is anything aside from VS 2015 itself (e.g., the Ultimate 2015 download on the preview page) needed? I'm assuming not. -- David ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Who's using VS/Windows to work on Python?
David Bolen wrote: > Steve Dower writes: > >> Also, who currently owns the Windows buildbots and are you >> willing/able to add a VS 2015 Preview installation (or give me access >> so I can do it)? (...) > > I've got several of the Windows buildbots, and could add this. Is there > benefit > to just starting with one (I've got XP, Win7 and Win8) first to save some > time? Starting with just the Win7 or Win8 one would be fine. Python 3.5 won't support XP, and VS 2015 doesn't support XP (though I believe it will still be able to build for XP, just not *on* XP). > My only real concern is to verify that this will co-exist properly with the > existing VS installations and buildbot build process. I note that the download > page says not to use on production computers. That's probably just a CYA, and > I > don't mind if VS itself has issues, but if it risks compromising other aspects > of the buildbot, then I think testing on a different machine would be > preferred. VS 2010 should be fine. The most likely issues are with VS 2013 (for teams that haven't updated their setup authoring yet), but these should have been ironed out already. > Is anything aside from VS 2015 itself (e.g., the Ultimate 2015 download on the > preview page) needed? I'm assuming not. Nope, that's it. I'll make sure there's a free version that will work eventually, but right now only Ultimate is available. I will make sure to let you know when the merge happens, but if VS 2015 is already there then that should be smooth anyway. Thanks, Steve > -- David ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Who's using VS/Windows to work on Python?
Steve Dower writes: > Starting with just the Win7 or Win8 one would be fine. Python 3.5 > won't support XP, and VS 2015 doesn't support XP (though I believe > it will still be able to build for XP, just not *on* XP). Ok, I'll probably try the Win8 buildbot first then. I'll let you know when it's available. FYI, the VS 2015 requirements page seems to include XP as a supported client OS (if I'm reading it correctly), and says the requirements are the same as for VS 2013. Of course, as you say it won't matter if we're dropping XP for Python 3.5. > VS 2010 should be fine. The most likely issues are with VS 2013 (for > teams that haven't updated their setup authoring yet), but these > should have been ironed out already. Ok, the buildbots are just VS 2008 and VS 2010, so no 2013 to worry about. > Nope, that's it. (...) Sounds good. -- David ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Who's using VS/Windows to work on Python?
On 14 November 2014 05:47, Steve Dower wrote: > Just wondering who is regularly/occasionally using VS 2010 to work on > Python? > > > > Also, who currently owns the Windows buildbots and are you willing/able to > add a VS 2015 Preview installation (or give me access so I can do it)? I > can also set up a VS 2015 buildbot, but the old ones will break if the > projects change (I should do this anyway to at least become familiar with > how the buildbots work…) > > > > > > I want to get a feel for who will be disrupted when I merge in the changes > to build with VS 2015, which will help influence when that merge occurs. VS > 2015 Preview was just released yesterday, and while it’s not perfect yet, > it’s isolated enough from VS 2010 that there won’t be any issues installing > them both (I can’t say the same for VS 2013…). If people are okay with > this, then we can consider merging the changes sooner. Once VS 2015 RC is > released, I’ll be looking to merge asap., but I don’t see a strong need to > do it before then other than a longer bake time. > With the recent (excellent) announcements around switching from the current Visual Studio Express model to the far more full featured Visual Studio Community approach, what will the situation be in relation to using Visual Studio Community edition to work on CPython? This thread, and Brian's post regarding renewing MSDN subscriptions made me realise we're going to need to be able to explain that to new Windows based contributors. Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
