|
From: Michael D. <md...@st...> - 2012-10-11 21:45:27
|
Thanks for taking this on, Damon and Gökhan.
Note this will need to create a different symlink (to dateutil_py3
instead) on Python 3. This means, of course, that it will be impossible
to develop on both Python 2 and 3 simultaneously, but that's true of
"setuptools' develop" in any event, so it's no great loss.
Mike
On 10/11/2012 03:38 PM, Damon McDougall wrote:
> On Thu, Oct 11, 2012 at 9:25 PM, Gökhan Sever <gok...@gm...> wrote:
>> I am not sure about that technical detail, but it works fine here on my
>> Fedora 16 (x86_64) system.
>>
>>
>> On Thu, Oct 11, 2012 at 11:04 AM, Damon McDougall
>> <dam...@gm...> wrote:
>>>
>>>
>>> On Thursday, October 11, 2012, Gökhan Sever wrote:
>>>>
>>>>
>>>> On Thu, Oct 11, 2012 at 3:49 AM, Damon McDougall
>>>> <dam...@gm...> wrote:
>>>>>
>>>>> Gökhan, did you implement the symlink fix? If so, would you mind
>>>>> making a pull request out of it? I was just about to look into doing
>>>>> this, but if you've done it already that'd save us some effort rolling
>>>>> out fixes for 1.2.
>>>>>
>>>>> Cheers.
>>>>> Damon
>>>>
>>>>
>>>> Hi Damon,
>>>>
>>>> I think adding these lines before execfile line in setupegg.py should fix
>>>> it:
>>>>
>>>> import os
>>>> os.chdir('lib')
>>>> if not os.path.isdir('dateutil'):
>>>> os.symlink('dateutil_py2', 'dateutil')
>>>> os.chdir('..')
>>>>
>>>>
>>>> Could you give it a test? Do we require a similar symlink for py3?
>>>>
>>>> Thanks.
>>>>
>>>>
>>>> --
>>>> Gökhan
>>>
>>> Awesome. I'll give it a go later on. I'm a little concerned using
>>> os.chdir. I think Peter Wuertz/Chris Gohlke had problems with it not being
>>> threadsafe on windows. Does the same apply here?
> I'm not sure how to test this. I'm running `setupegg.py develop` from
> within a python virtual env, but somehow it's picking up dateutil
> version 1.5. I don't get the `matplotlib will provide` message... Hmm.
>
|