Re: python-virtualenv 0.10.1-1
On Wed, Aug 14, 2013 at 8:14 PM, Barry Warsaw wrote: > > This one was on my list, so thanks for getting to it before I did. :) > > I did some minimal testing. It built fine, and I could create Python 2.7 and > 3.3 virtualenvs, and pip install a few packages into both. A cursory look at > the diff also seems fine and lintian is happy. I'd say go for it. Thanks! I've uploaded it (with one more change suggested by lintian4py). -- mithrandi, i Ainil en-Balandor, a faer Ambar -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/camckhmq5-g1fho2hyds8bfsodije_c_4bhufbokszwxmvpn...@mail.gmail.com
Re: python-virtualenv 0.10.1-1
On Aug 14, 2013, at 06:30 PM, Tristan Seligmann wrote: >I've updated python-virtualenv in DPMT SVN for the latest upstream release >(0.10.1). Among other things, this fixes an issue where running tox with >$PYTHONDONTWRITEBYTECODE set would fail with an error from virtualenv. > >The changes were fairly straightforward (dropping an obsolete patch, and >some renamed/removed files) but as I am a very infrequent user of >virtualenv I haven't uploaded the new version; I'd appreciate it if >somebody more familiar with the package could take a look to make sure I >didn't break anything. This one was on my list, so thanks for getting to it before I did. :) I did some minimal testing. It built fine, and I could create Python 2.7 and 3.3 virtualenvs, and pip install a few packages into both. A cursory look at the diff also seems fine and lintian is happy. I'd say go for it. -Barry -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130814141445.58c75fec@anarchist
python-virtualenv 0.10.1-1
I've updated python-virtualenv in DPMT SVN for the latest upstream release (0.10.1). Among other things, this fixes an issue where running tox with $PYTHONDONTWRITEBYTECODE set would fail with an error from virtualenv. The changes were fairly straightforward (dropping an obsolete patch, and some renamed/removed files) but as I am a very infrequent user of virtualenv I haven't uploaded the new version; I'd appreciate it if somebody more familiar with the package could take a look to make sure I didn't break anything. -- mithrandi, i Ainil en-Balandor, a faer Ambar