Hi Erica,

I would first try Roman's solution. However, a member of my team is
rewriting the PySide build scripts to update them, support
pyenv<https://github.com/yyuu/pyenv>,
and in general simplify them. I believe they are updated to build with the
stable 1.2.1. You can find his work
here<https://github.com/midimaster21b/BuildScripts/tree/rewrite>-- make
sure you check out the
rewrite branch.

I don't know if you've used the build scripts before, but the only change
you should have to make is to change the PREFIX variable in
environment.shto match the prefix of the virtualenv itself.

Good luck!


--
Sean Fisk


On Mon, Mar 3, 2014 at 7:05 PM, Roman Lacko <backup.rla...@gmail.com> wrote:

> Hi,
>
> You can also install PySide with pip directli from git repository.
>
> This should work, but have not tested with latest version:
> pip install 
> git+ssh://github.com/PySide/pyside-setup.git<https://github.com/username/repo.git>
>
> -Roman
>
> 2014-03-03 23:23 GMT+01:00 Erica Cane <ericac...@splitu.com>:
>
> Thanks Sean. I am indeed interested in compiling from source in a
>> virtualenv. That said, the ideal solution would be for the PyPi package to
>> be updated with the fix for Mavericks. :)
>>
>> Thanks again!
>> Erica
>>
>>
>> On Sun, Mar 2, 2014 at 10:44 PM, Sean Fisk <s...@seanfisk.com> wrote:
>>
>>> When compiling from source, you can install into a virtualenv. When
>>> using Homebrew, it's not possible to install into a virtualenv.
>>>
>>> I don't use Homebrew's Python, and don't install any other Python
>>> packages other than PySide. Then, inside of the virtualenv, I use a PTH
>>> file <http://docs.python.org/2/library/site.html> to point to
>>> Homebrew's site-packages/ directory. Unfortunately, this also includes
>>> any other Python packages installed by Homebrew if you decide to install
>>> them. It's not the best option, but it works well. I can send you my
>>> PTH-file-writing-script if you are interested.
>>>
>>> If you are interested in compiling from source into a virtualenv, my
>>> team is working on improving the PySide 
>>> BuildScripts<https://github.com/PySide/BuildScripts>repo and I can send you 
>>> what we have as well.
>>>
>>> If you are interested in either of these, expect a reply from me
>>> tomorrow as it is pretty late in my neck of the woods.
>>>
>>> Cheers,
>>>
>>>
>>> --
>>> Sean Fisk
>>>
>>>
>>> On Mon, Mar 3, 2014 at 1:29 AM, Erica Cane <ericac...@splitu.com> wrote:
>>>
>>>> Thanks for the responses Ryan and Sean.
>>>>
>>>> Is it possible to use homebrew or source to install into a virtualenv?
>>>>
>>>>
>>>> On Sun, Mar 2, 2014 at 10:06 PM, Sean Fisk <s...@seanfisk.com> wrote:
>>>>
>>>>> Hi Erica,
>>>>>
>>>>> This won't fix the PyPi issue, but I usually install on Mac OS X using
>>>>> Homebrew <http://brew.sh/>. Though that has had some recent issues as
>>>>> well.
>>>>>
>>>>> Cheers,
>>>>>
>>>>>
>>>>> --
>>>>> Sean Fisk
>>>>>
>>>>>
>>>>> On Sun, Mar 2, 2014 at 6:47 PM, Erica B. <ericac...@splitu.com> wrote:
>>>>>
>>>>>>  Hi all,
>>>>>>
>>>>>> I'm attempting to install pyside via pip on my Macbook Pro running OS
>>>>>> X 10.9.2 (Mavericks) and am running into some issues. The install fails
>>>>>> with the following error:
>>>>>>
>>>>>> /build/PySide/sources/shiboken/ext/sparsehash/google/dense_hash_map:97:10:
>>>>>>> fatal error: 'tr1/functional' file not found
>>>>>>> #include HASH_FUN_H                  // defined in config.h
>>>>>>>          ^
>>>>>>> /build/PySide/sources/shiboken/ext/sparsehash/google/sparsehash/sparseconfig.h:18:24:
>>>>>>> note: expanded from macro 'HASH_FUN_H'
>>>>>>>     #define HASH_FUN_H <tr1/functional>
>>>>>>>                        ^
>>>>>>> 1 error generated.
>>>>>>> make[2]: ***
>>>>>>> [libshiboken/CMakeFiles/libshiboken.dir/sbkconverter.cpp.o] Error 1
>>>>>>> make[1]: *** [libshiboken/CMakeFiles/libshiboken.dir/all] Error 2
>>>>>>> make: *** [all] Error 2
>>>>>>> error: Error compiling shiboken
>>>>>>
>>>>>>
>>>>>> After some searching, it seems this is a Mavericks error and may have
>>>>>> been fixed in November (
>>>>>> https://codereview.qt-project.org/#change,69324), but that change
>>>>>> hasn't made its way to PyPi (https://pypi.python.org/pypi/PySide).
>>>>>> If this is the case, perhaps the PyPi package could use a refresh. If 
>>>>>> not,
>>>>>> any ideas what can be done to fix the error?
>>>>>>
>>>>>> Thanks!
>>>>>> Erica
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>>
>>>>>> PySide mailing list
>>>>>> PySide@qt-project.org
>>>>>> http://lists.qt-project.org/mailman/listinfo/pyside
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>> _______________________________________________
>> PySide mailing list
>> PySide@qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/pyside
>>
>>
>
_______________________________________________
PySide mailing list
PySide@qt-project.org
http://lists.qt-project.org/mailman/listinfo/pyside

Reply via email to