On Tue, Mar 29, 2016 at 4:08 PM, Pietro wrote:
> On Tue, Mar 29, 2016 at 3:12 PM, Vaclav Petras wrote:
>>
>> On Tue, Mar 29, 2016 at 5:33 AM, Pietro wrote:
>>>
>>> I have fixed these errors, but since these changes are not fixing
On Tue, Mar 29, 2016 at 3:12 PM, Vaclav Petras wrote:
>
> On Tue, Mar 29, 2016 at 5:33 AM, Pietro wrote:
>>
>> I have fixed these errors, but since these changes are not fixing
>> bugs, I've just reverted them. I will commit these change back to
>>
Hi,
2016-03-29 15:12 GMT+02:00 Vaclav Petras :
> I hope this won't become a common practice. I think trunk is where the
> development happens. It is not a stable branch regardless of any plans.
> Should I also revert all my non-bugfixes from last weeks? If needed, I can
>
On Tue, Mar 29, 2016 at 5:33 AM, Pietro wrote:
> I have fixed these errors, but since these changes are not fixing
> bugs, I've just reverted them. I will commit these change back to
> trunk as soon as we can start working on grass72.
>
I hope this won't become a common
Hi Vaclav,
On Fri, Mar 25, 2016 at 8:38 PM, Vaclav Petras wrote:
> Nice! But please, check the tests:
>
> http://fatra.cnr.ncsu.edu/grassgistests/reports_for_date-2016-03-25-07-00/report_for_nc_basic_spm_grass7_nc/lib/python/gunittest/test_doctests/index.html
>
On Fri, Mar 25, 2016 at 2:14 AM, Pietro wrote:
>
> I commit some changes in pygrass (r68138), temporal library (r68139)
> and GRASS scripts (r68140) that were on my trunk from a bit...
Nice! But please, check the tests:
On Thu, Mar 24, 2016 at 12:52 AM, Luca Delucchi wrote:
> On 13 March 2016 at 10:52, Maris Nartiss wrote:
>> I personally would like to see adoption of PEP8 and moving all python
>> code to be python3 ready. As old python versions are dying out, there
>>
On 13 March 2016 at 10:52, Maris Nartiss wrote:
> I personally would like to see adoption of PEP8 and moving all python
> code to be python3 ready. As old python versions are dying out, there
> is less and less initiative to not do so.
> Also related to
>
Maciej Sieczka wrote:
> What are the prospects, if any, for GRASS Python code to conform to
> https://www.python.org/dev/peps/pep-0394 ?
>
> Not a huge issue to me personally. I'm just curious about GRASS team
> opinions on this matter. It might be worth considering. At least in the
> future,
I personally would like to see adoption of PEP8 and moving all python
code to be python3 ready. As old python versions are dying out, there
is less and less initiative to not do so.
Also related to
https://lists.osgeo.org/pipermail/grass-dev/2016-February/078828.html
Māris.
2016-03-12 22:56
Hi,
What are the prospects, if any, for GRASS Python code to conform to
https://www.python.org/dev/peps/pep-0394 ?
Not a huge issue to me personally. I'm just curious about GRASS team
opinions on this matter. It might be worth considering. At least in the
future, when more distros move to
11 matches
Mail list logo