Re: Wrong translation in Brazillian portuguese

[Bruno Ribeiro da Silva]

Thanks, I request to join the Brazillian portuguese at transifex, I'm gonna
wait the approval to fix the translations.


On Mon, Apr 7, 2014 at 12:12 PM, Andrew Farrell wrote:

> According to https://code.djangoproject.com/wiki/Version1.7Roadmap, the
> translation string freeze is not until the 1st of May, so it should be.
>
> -- Andrew
>
>
> On Mon, Apr 7, 2014 at 10:45 AM, Bruno Ribeiro da Silva <
> bruno.dev...@gmail.com> wrote:
>
>> Hi everyone,
>>
>> I found a wrong translation in Brazillian portuguese that affects django
>> 1.7 and it's present in master too. I'm going to open a ticket for this and
>> make a pull request. Do you think it's possible to fix for the 1.7?
>>
>> Thank you!
>>
>> --
>> Bruno Ribeiro da Silva
>> Python Dev and Homebrewer!
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to django-developers+unsubscr...@googlegroups.com.
>> To post to this group, send email to django-developers@googlegroups.com.
>> Visit this group at http://groups.google.com/group/django-developers.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-developers/CAE-2%3DJyri-hr-Q9%2BzdezBxkLG2-qzViBQmF9bwotmPFBvZ%3DS%3Dg%40mail.gmail.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/CA%2By5TLZFRmb2x0r%2Bwjk3GJXaiAyddUZ_X_auRg%3Dq2RBQqZvXCQ%40mail.gmail.com
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Bruno Ribeiro da Silva
Python Dev and Homebrewer!

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAE-2%3DJzSFyGCj9Y0pTR3TZR4QJkBPTVhx9c%3D8DmLokbXTsXnaw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Wrong translation in Brazillian portuguese

[Andrew Farrell]

According to https://code.djangoproject.com/wiki/Version1.7Roadmap, the
translation string freeze is not until the 1st of May, so it should be.

-- Andrew

On Mon, Apr 7, 2014 at 10:45 AM, Bruno Ribeiro da Silva <
bruno.dev...@gmail.com> wrote:

> Hi everyone,
>
> I found a wrong translation in Brazillian portuguese that affects django
> 1.7 and it's present in master too. I'm going to open a ticket for this and
> make a pull request. Do you think it's possible to fix for the 1.7?
>
> Thank you!
>
> --
> Bruno Ribeiro da Silva
> Python Dev and Homebrewer!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/CAE-2%3DJyri-hr-Q9%2BzdezBxkLG2-qzViBQmF9bwotmPFBvZ%3DS%3Dg%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CA%2By5TLZFRmb2x0r%2Bwjk3GJXaiAyddUZ_X_auRg%3Dq2RBQqZvXCQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Wrong translation in Brazillian portuguese

[Baptiste Mispelon]

Hi,

Django's translations are managed on a separate website called transifex.
You can find more information on the translation process on our 
documentation at 
https://docs.djangoproject.com/en/1.6/internals/contributing/localizing/#translations.


As far as I know, the window for the 1.7 translations is still open so 
if you fix the translation on transifex, it should make its way into the 
final 1.7 release.



Thanks,
Baptiste

On 04/07/2014 04:45 PM, Bruno Ribeiro da Silva wrote:

Hi everyone,

I found a wrong translation in Brazillian portuguese that affects 
django 1.7 and it's present in master too. I'm going to open a ticket 
for this and make a pull request. Do you think it's possible to fix 
for the 1.7?


Thank you!

--
Bruno Ribeiro da Silva
Python Dev and Homebrewer!
--
You received this message because you are subscribed to the Google 
Groups "Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to django-developers+unsubscr...@googlegroups.com 
.
To post to this group, send email to 
django-developers@googlegroups.com 
.

Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAE-2%3DJyri-hr-Q9%2BzdezBxkLG2-qzViBQmF9bwotmPFBvZ%3DS%3Dg%40mail.gmail.com 
.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups "Django 
developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/5342C0CF.4000406%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Wrong translation in Brazillian portuguese

[Bruno Ribeiro da Silva]

Hi everyone,

I found a wrong translation in Brazillian portuguese that affects django
1.7 and it's present in master too. I'm going to open a ticket for this and
make a pull request. Do you think it's possible to fix for the 1.7?

Thank you!

-- 
Bruno Ribeiro da Silva
Python Dev and Homebrewer!

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAE-2%3DJyri-hr-Q9%2BzdezBxkLG2-qzViBQmF9bwotmPFBvZ%3DS%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSOC] Shifting to Py.Test and Improving the Test Suite

[Aymeric Augustin]

Before this thread goes too far, I'd like to express my doubts regarding
the goals you stated.

2014-02-27 20:50 GMT+01:00 Akshay Jaggi :

>
> *Need for Improvement/ Current Problems*
>
>1. Running of Test Cases is slow.
>
> I don't know what the threshold for "slow" is, but faster is obviously
better ;-) However, could you clarify how changing the test runner will
make the tests run faster?

I gained a little bit of experience in that area when I helped divide by
three the run time of the test suite last year. I don't believe unittest
even registers on the radar of things that make the tests slow. If you
haven't heard the "Database is Hot Lava" meme, google it.

>
>1. Selection of what tests we want to run, and what all we don't want
>to run is difficult
>
> That problem can be solved by a custom test runner extending unittest,
without changing -- and maybe breaking -- the semantics of the tests.

I've been working on this codebase for some time and I have a hard time to
believe someone will actually audit all of the 5000 test cases. Some are
really tricky -- like, with threads, database transactions, hacks for
in-memory SQLite, and some selenium.

>
>1. We have better options available
>
> It's hard to take such a blanket statement at face value. You need to
argue why py.test is better *for Django*. For starters, using standard
tools from the standard library helps lowering the barrier to contributing.
Every change must come with a test, and if that involves learning a new
test runner and a complex categorisation system, that's an additional
barrier.

Don't get me wrong -- I know that py.test is a good tool. I'm just saying
that you shouldn't start rewriting chunks of Django's test suite without
convincing the core team that you understand the problem you're trying to
solve.

-- 
Aymeric.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CANE-7mWBMHmj3nCwbid0eusDDte52jfEa2ab-_1nxQjV74_HVQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSOC] Shifting to Py.Test and Improving the Test Suite

[Andreas Pelme]

Hi Chris,

It looks like you invoke nosetests and not py.test, therefore you do not get 
the results one would expect with py.test:

On 7 apr 2014, at 11:52, Chris Wilson  wrote:
> OK, here is one.
> 
> chris@lap-x201:~/projects/2014/webassets$ .ve/bin/tox -e py27 -- 
> tests.test_filters:TestPyScss.test_search_path

...

> py27 runtests: commands[0] | nose tests 
> tests.test_filters:TestPyScss.test_search_path

...

>  File 
> "/home/chris/projects/2014/webassets/.tox/py27/local/lib/python2.7/site-packages/nose/case.py",
>  line 197, in runTest


This is what the output from a similar test with pytest would result in: 
(Screenshot at http://pelme.se/~andreas/private/pytest_assertion.png to give 
the correct colors/formatting.)

$ py.test test_foo.py
= test session starts 
==
platform darwin -- Python 2.7.5 -- pytest-2.5.2.dev1
plugins: xdist
collected 1 items

test_foo.py F

=== FAILURES 
===
 test_something 


def test_something():
foo = {'out.css': 'something'}
>   assert foo.get('out.css') == 'h1 {\n  color: #ff;\n}\na {\n color: 
> #ff8000;\n}\n'
E   assert 'something' == 'h1 {\n  color: #ff...\n color: #ff8000;\n}\n'
E - something
E + h1 {
E +   color: #ff;
E + }
E + a {
E +  color: #ff8000;
E + }

test_foo.py:4: AssertionError
=== 1 failed in 0.01 seconds 
===



Cheers,
Andreas

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/38638CE1-A189-4954-A412-FE77908436AA%40pelme.se.
For more options, visit https://groups.google.com/d/optout.

Re: [GSOC] Shifting to Py.Test and Improving the Test Suite

[Chris Wilson]

Hi Andrew,

On Sun, 6 Apr 2014, Chris Wilson wrote:

On Sun, 6 Apr 2014, Andrew Pashkin wrote:

* It makes it much harder to write custom assertions and get meaningful 
display on error.


Can you give an examples for cases with messages/breakings and for custom 
assertions?


I don't have an example of breakage to hand, I ripped out the offending code 
in disgust and replaced it with standard assertions that worked. If I find 
another example I'll be sure to let you know before I do the same again.


OK, here is one.

chris@lap-x201:~/projects/2014/webassets$ .ve/bin/tox -e py27 -- 
tests.test_filters:TestPyScss.test_search_path

GLOB sdist-make: /home/chris/projects/2014/webassets/setup.py
py27 inst-nodeps: 
/home/chris/projects/2014/webassets/.tox/dist/webassets-0.10.dev.zip

py27 runtests: PYTHONHASHSEED='894115171'
py27 runtests: commands[0] | nosetests 
tests.test_filters:TestPyScss.test_search_path

F
==
FAIL: tests.test_filters.TestPyScss.test_search_path
--
Traceback (most recent call last):
  File 
"/home/chris/projects/2014/webassets/.tox/py27/local/lib/python2.7/site-packages/nose/case.py", 
line 197, in runTest

self.test(*self.arg)
  File "/home/chris/projects/2014/webassets/tests/test_filters.py", line 
969, in test_search_path
assert self.get('out.css') == 'h1 {\n  color: #ff;\n}\na {\n 
color: #ff8000;\n}\n'

AssertionError

--
Ran 1 test in 0.055s

FAILED (failures=1)

"AssertionError". Gee, thanks. That helps a lot. So if the string wasn't 
what we expected, what WAS it? How is this anywhere NEAR as useful as 
self.assertEqual()?


Cheers, Chris.
--
Aptivate | http://www.aptivate.org | Phone: +44 1223 967 838
Citylife House, Sturton Street, Cambridge, CB1 2QF, UK

Aptivate is a not-for-profit company registered in England and Wales
with company number 04980791.

--
You received this message because you are subscribed to the Google Groups "Django 
developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/alpine.DEB.2.02.1404071049580.7500%40lap-x201.
For more options, visit https://groups.google.com/d/optout.