14.01.2013 14:44, Matthew Brett kirjoitti:
[clip]
> Pierre's suggestion is good; you can also do something like this:
>
> # -*- coding: utf8 -*-
> import sys
>
> if sys.version_info[0] >= 3:
> a = 'öäöäöäöäö'
> else:
> a = unicode('öäöäöäöäö', 'utf8')
>
> The 'coding' line has to
On 01/14/2013 02:44 PM, Matthew Brett wrote:
> On Mon, Jan 14, 2013 at 10:35 AM, Jaakko Luttinen
> wrote:
>> On 01/14/2013 12:53 AM, Matthew Brett wrote:
>>> You might be able to get away without 2to3, using the kind of stuff
>>> that Pauli has used for scipy recently:
>>>
>>> https://github.com/s
Hi,
On Mon, Jan 14, 2013 at 10:35 AM, Jaakko Luttinen
wrote:
> On 01/14/2013 12:53 AM, Matthew Brett wrote:
>> On Sun, Jan 13, 2013 at 10:46 PM, Jaakko Luttinen
>> wrote:
>>> I'm a bit stuck trying to make numpydoc Python 3 compatible. I made
>>> setup.py try to use distutils.command.build_py.bu
Hi,
Le 14/01/2013 11:35, Jaakko Luttinen a écrit :
> Ok, thanks, maybe I'll try to make the tests valid in all Python
> versions. It seems there's only one line which I'm not able to transform.
>
> In doc/sphinxext/tests/test_docscrape.py, on line 559:
> assert doc['Summary'][0] == u'öäöäöäöäö
On 01/14/2013 12:53 AM, Matthew Brett wrote:
> On Sun, Jan 13, 2013 at 10:46 PM, Jaakko Luttinen
> wrote:
>> I'm a bit stuck trying to make numpydoc Python 3 compatible. I made
>> setup.py try to use distutils.command.build_py.build_py_2to3 in order to
>> transform installed code automatically to
Hi,
On Sun, Jan 13, 2013 at 10:46 PM, Jaakko Luttinen
wrote:
> On 2013-01-10 17:16, Jaakko Luttinen wrote:
>> On 01/10/2013 05:04 PM, Pauli Virtanen wrote:
>>> Jaakko Luttinen aalto.fi> writes:
The files in numpy/doc/sphinxext/ and numpydoc/ (from PyPI) are a bit
different. Which ones
On 2013-01-10 17:16, Jaakko Luttinen wrote:
> On 01/10/2013 05:04 PM, Pauli Virtanen wrote:
>> Jaakko Luttinen aalto.fi> writes:
>>> The files in numpy/doc/sphinxext/ and numpydoc/ (from PyPI) are a bit
>>> different. Which ones should be modified?
>>
>> The stuff in sphinxext/ is the development
On 01/10/2013 05:04 PM, Pauli Virtanen wrote:
> Jaakko Luttinen aalto.fi> writes:
>> The files in numpy/doc/sphinxext/ and numpydoc/ (from PyPI) are a bit
>> different. Which ones should be modified?
>
> The stuff in sphinxext/ is the development version of the package on
> PyPi, so the changes s
Jaakko Luttinen aalto.fi> writes:
> The files in numpy/doc/sphinxext/ and numpydoc/ (from PyPI) are a bit
> different. Which ones should be modified?
The stuff in sphinxext/ is the development version of the package on
PyPi, so the changes should be made in sphinxext/
--
Pauli Virtanen
___
The files in numpy/doc/sphinxext/ and numpydoc/ (from PyPI) are a bit
different. Which ones should be modified?
-Jaakko
On 01/10/2013 02:04 PM, Pauli Virtanen wrote:
> Hi,
>
> Jaakko Luttinen aalto.fi> writes:
>> I'm trying to use numpydoc (Sphinx extension) for my project written in
>> Python 3
Hi,
Jaakko Luttinen aalto.fi> writes:
> I'm trying to use numpydoc (Sphinx extension) for my project written in
> Python 3.2. However, installing numpydoc gives errors shown at
> http://pastebin.com/MPED6v9G and although it says "Successfully
> installed numpydoc", trying to import numpydoc raise
Hi!
I'm trying to use numpydoc (Sphinx extension) for my project written in
Python 3.2. However, installing numpydoc gives errors shown at
http://pastebin.com/MPED6v9G and although it says "Successfully
installed numpydoc", trying to import numpydoc raises errors..
Could this be fixed or am I doi
12 matches
Mail list logo
