I'd like there to be an e-build for virtualenvwrapper[0]. It's a nice utility that makes virtualenv a little easier to work with. [0] http://www.doughellmann.com/projects/virtualenvwrapper/ Reproducible: Always
*** This bug has been confirmed by popular vote. ***
Created attachment 271585 [details] virtualenvwrapper-2.7.1.ebuild I found an ebuild from http://www.iwangbin.com/blog/2010/10/18/virtualenvwrapper-ebuild-for-gentoo/ and I updated it for the latest version of virtualenvwrapper.
Hello, The Gentoo Team would like to firstly thank you for your ebuild submission. We also apologize for not being able to accommodate you in a timely manner. There are simply too many new packages. Allow me to use this opportunity to introduce you to Gentoo Sunrise. The sunrise overlay[1] is a overlay for Gentoo which we allow trusted users to commit to and all users can have ebuilds reviewed by Gentoo devs for entry into the overlay. So, the sunrise team is suggesting that you look into this and submit your ebuild to the overlay where even *you* can commit to. =) Thanks, On behalf of the Gentoo Sunrise Team, Markos. [1]: http://www.gentoo.org/proj/en/sunrise/ [2]: http://overlays.gentoo.org/proj/sunrise/wiki/SunriseFaq
Created attachment 294059 [details] Updated virtualenvwrapper ebuild I'd make a patch since I saw a keyword InVCS, but I can't find it so a full ebuild. I've bumped EAPI to 4, updated SRC_URI to use more variables and I've added setuptools to [R]DEPEND since it uses pkg_resources. I would be interested in maintaining this package through a proxy.
Ewoud, sounds great. Would you be able to come hang out in #gentoo-python on IRC?
Created attachment 297379 [details] virtualenvwrapper-2.11.ebuild My version of virtualenvwrapper ebuild
How may I help get this into the main tree? Here is what I have for virtualenvwrapper-3.0 (very basic): https://github.com/npinto/sekyfsr-gentoo-overlay/blob/master/dev-python/virtualenvwrapper/virtualenvwrapper-3.0.ebuild Let me know.
For you, too: come hang out in #gentoo-python on freenode (if at all possible), and we'll do some review.
Today, after the upgrade, I found that most of the ports tree, a new version of virtualenv. After you upgrade to a newer version virtualenvwrapper stopped working. The problem is that with the package is not installed pth-file and, accordingly, the interpreter python can not find the newly installed package. When you install the following message appears: * * Python namespaces: * '/usr/lib64/python2.7/site-packages/virtualenvwrapper-3.0-py2.7-nspkg.pth': * virtualenvwrapper * However, the file in the specified path does not exists.
The problem was much simpler. =) In the directory /usr/lib/python2.7/site-packages/virtualenvwrapper/ missing __init__.py file.
I just noticed 3.0 entered the tree and totally forgot about this. Apparently I forgot to CC myself :( With 3.0 I have an issue with no hook loader. When I source `which virtualenvwrapper.sh` I get the following traceback: Traceback (most recent call last): File "<string>", line 1, in <module> ImportError: No module named virtualenvwrapper.hook_loader Secondly the dependency seems weird: RDEPEND="dev-python/virtualenv" DEPEND="${DEPEND} I'd expect virtualenv to be a build dependency.
It seems my first issue is the same as Suloev Dmitry, creating an empty __init__.py solves my issues.
We'll discuss the issue noted in comment 11 in bug 404103, please.
