Re: Can anyone please explain the below code???

[Bruno Ribeiro da Silva]

Wrong list, this is for development related only.

I suggest you read django's documentation
https://docs.djangoproject.com/en/1.11/

2017-10-06 8:05 GMT-03:00 <utpalbrahma1...@gmail.com>:

> from django.db import models
>
> class Question(models.Model):
> question_text = models.CharField(max_length=200)
> pub_date = models.DateTimeField('date published')
>
> class Choice(models.Model):
> question = models.ForeignKey(Question, on_delete=models.CASCADE)
> choice_text = models.CharField(max_length=200)
> votes = models.IntegerField(default=0)
>
> My question
> 1.What is models.Models?
> 2.What are the attributes of models?
> 3.What are the attributes of Models?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" 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 https://groups.google.com/group/django-developers.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/django-developers/ac101a4b-4fb9-4d7c-abee-
> effbd61062d3%40googlegroups.com
> <https://groups.google.com/d/msgid/django-developers/ac101a4b-4fb9-4d7c-abee-effbd61062d3%40googlegroups.com?utm_medium=email_source=footer>
> .
> 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  (Contributions to Django itself)" 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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAE-2%3DJy%2B-6oJY8PP58EqQODKW01mU5krtdnrj3Eur6UfcvYRZA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Feature idea

[Bruno Ribeiro da Silva]

Guys,

Thanks for the feedback. My initial thought was to have a more complete
approach to this problem, there is always the case that the admin who is
creating the user doesn't know the person's full name and/or what to use
for username.

This is the flow that I had in mind:

- Admin goes to user list page
- Next to the "ADD USER +" button we would have an "INVITE NEW USER" button
- At the invite page the admin would only have to insert the person's email
address. Optionally he could check if this new user would be a super user
and/or staff.
- At the invitation (link sent by email) page the user would be able to
fill the rest of the information, like: username, first name, last name and
password.

I know this approach requires more work but I think it would be nice to
free the admin from the burden of having to fill all necessary information.


2016-11-17 6:44 GMT-02:00 Curtis Maloney <cur...@tinbrain.net>:

> My solution to the "initial password problem" is to send a password reset
> token first...
>
> And Django has this built in, handily :)
>
> http://musings.tinbrain.net/blog/2014/sep/21/registration-django-easy-way/
>
> It would be very easy to use the same approach for an "invite"
> registration pattern.
>
> --
> C
>
>
> On 17/11/16 19:38, Aymeric Augustin wrote:
>
>> Hello,
>>
>> On 16 Nov 2016, at 21:22, Anthony King <anthonydk...@gmail.com
>>> <mailto:anthonydk...@gmail.com>> wrote:
>>>
>>> Sending a link to set a password isn't much better.
>>>
>>> The cardinal rule of passwords is “you must be the only person who knows
>> your password”. This means never writing it down anywhere, except in a
>> proper password manager, and never telling it to anyone, *even* your IT
>> staff — to fight social engineering attacks.
>>
>> Sending a password in clear over email means the IT staff is okay with
>> knowing the user's password. Disregarding their own guidelines sets a
>> poor example and reduces their credibility about password management in
>> general.
>>
>> Of course, on most Django websites, someone who can create a staff user
>> can also change the user’s password — it’s rare to give the “create
>> user” but not the “change user” permission. I’m not making a technical
>> argument here, I’m thinking of IT literacy and educating users.
>>
>> Perhaps a way to force a password change on login would be better,
>>> which has more use elsewhere, such as being able to periodically force
>>> password changes
>>>
>>
>> Forcing a password change on login is another interesting idea to solve
>> this problem. That’s what ActiveDirectory has to do, because OSes don’t
>> have the same password reset possibilities that web applications have.
>>
>> However I think that would mean solving the general problem of password
>> rotation. Django solved password validation recently; it could solve
>> password rotation next. (Note that password rotation is controversial
>> because it forces users to choose weak passwords with a basic rotation
>> scheme like putting month number at the end, instead of storing strong
>> random password in a password manager. Trade-offs.)
>>
>> I still think a simple solution hooking into the current password reset
>> mechanism, just with a different email template, could be a quick
>> security win for a lot of Django sites. I’d encourage people to use it
>> if it existed.
>>
>> Best regards,
>>
>> --
>> Aymeric.
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Django developers (Contributions to Django itself)" group.
>> To unsubscribe from this group and stop receiving emails from it, send
>> an email to django-developers+unsubscr...@googlegroups.com
>> <mailto:django-developers+unsubscr...@googlegroups.com>.
>> To post to this group, send email to django-developers@googlegroups.com
>> <mailto:django-developers@googlegroups.com>.
>> Visit this group at https://groups.google.com/group/django-developers.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-developers/76AE3F1E
>> -6C00-4E4E-86A7-4E1374FF20AF%40polytechnique.org
>> <https://groups.google.com/d/msgid/django-developers/76AE3F1
>> E-6C00-4E4E-86A7-4E1374FF20AF%40polytechnique.org?utm_
>> medium=email_source=footer>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers  (Contributions t

Feature idea

[Bruno Ribeiro da Silva]

Hello everyone,

I have this simple idea that I think django could benefit from, which would
be the option to create a user by an invitation from the django admin page.
So the person who is creating a new user doesn't have to type a password
neither a username for this new user. He would only fill a form with an
email that the invitation would be sent to. Something like a reset password
link but to add a new user.

Do you think it would be useful? That would be accepted as a PR for some
version in the future? What are your thoughts?

I would like to implement it and contribute to django, but I need feedback
from you guys.


Thanks!

-- 
Bruno Ribeiro da Silva
Python Dev and Homebrewer!

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" 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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAE-2%3DJyOPhTiq5kWKrcZHLBdxWu3JvVvwj8iXEJXZW0KmmJeAw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Use migrations api to create a command for data migration between different databases

[Bruno Ribeiro da Silva]

I agree with you Shai, that's why I proposed a command that makes use of
migrations internals (not to use a migration per se) to do the job.

Thanks for the feedback Marc, I know having the migration to use django orm
is a much slower process than importing it from a textual source, but the
main objective is the correctness of the data. Using django orm would
guarantee that all the tables are created the way django expects it and the
data is inserted into the database as well as the way django does it.

My concern is migrate without having to change anything on the models or
get an unexpected behavior.

Thanks for all your feedback, I'm gonna try to have some PoC and see if
it's doable.

On Tue, Jun 14, 2016 at 8:43 AM, Shai Berger <s...@platonix.com> wrote:

> Hi Bruno,
>
> I think that putting such an operation in a migration doesn't make much
> sense. If it's part of the project migrations, it means that the canonical
> way to set up the database is to start up on MySQL and move to PG later.
> This is almost surely not what you intend.
>
> Copying data across is usually a one-time thing, not something you want as
> part of your living history. A management command fits much better than a
> migration.
>
> My 2 cents,
> Shai
>
> On 10 ביוני 2016 20:47:51 GMT+03:00, Bruno Ribeiro da Silva <
> bruno.dev...@gmail.com> wrote:
>>
>> Hey guys, I'm not sure if I should be asking this here, but it's related
>> to django internals.
>>
>> I have this idea to create a command that uses the migrations api to
>> migrate all the data from one database (eg. MySQL) to another database
>> (PostgreSQL).
>>
>> So I would run the migrations in the new target database, then flush all
>> the tables there, and model by model do a bunch of bulk_create into the new
>> database using the result queryset from the source database.
>>
>>
>> The questions are: do you think it is feasible to make all of this inside
>> a command? If I have to change the migrations api to make it happen, do you
>> think this could be a nice feature to have in Django?
>>
>>
>> Thanks in advance!
>>
>>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" 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 https://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/9B1A79E7-E458-4DA5-BC94-C1838DA4908E%40platonix.com
> <https://groups.google.com/d/msgid/django-developers/9B1A79E7-E458-4DA5-BC94-C1838DA4908E%40platonix.com?utm_medium=email_source=footer>
> .
>
> 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  (Contributions to Django itself)" 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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAE-2%3DJyeqJMwkh%3Dw-VA9b1ou4nz-juE9kwYvG5HJB5-AfRcKZQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Use migrations api to create a command for data migration between different databases

[Bruno Ribeiro da Silva]

Hey guys, I'm not sure if I should be asking this here, but it's related to 
django internals.

I have this idea to create a command that uses the migrations api to 
migrate all the data from one database (eg. MySQL) to another database 
(PostgreSQL).

So I would run the migrations in the new target database, then flush all 
the tables there, and model by model do a bunch of bulk_create into the new 
database using the result queryset from the source database.


The questions are: do you think it is feasible to make all of this inside a 
command? If I have to change the migrations api to make it happen, do you 
think this could be a nice feature to have in Django?


Thanks in advance!

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" 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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/1f588512-dc82-4182-a87b-cbdabea71a11%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: DKIM signing option for stmp.MailBackend?

[Bruno Ribeiro da Silva]

I do think DKIM is a task for the MTA too, so it doesn't make much sense to
have it in django's core.
On Apr 4, 2015 6:27 AM, "Claude Paroz"  wrote:

> Le vendredi 3 avril 2015 19:05:02 UTC+2, Loek van Gent a écrit :
>>
>> Hi all,
>>
>> Is anyone using DKIM signing for densing emails? Does it make sense to
>> you to have a feature like that in Django core or is this typically
>> something that should be in it's own app?
>>
>
> I think that generally DKIM is most often a task of the MTA (mail transfer
> agent), while Django is playing the role of the MUA (user agent) here.
> Hence I wouldn't push for a Django core integration, but more as an
> external add-on.
>
> Claude
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" 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/21692a8d-f5c3-4389-83a5-b7fdb4c445d5%40googlegroups.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  (Contributions to Django itself)" 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%3DJztAorZA6yNa4ZsWvhMUEovZ%3DW5_9SoiQGueLU%2Bvdb%2BdA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django Admin New Look

[Bruno Ribeiro da Silva]

Looks good! Congrats!

On Wed, Mar 11, 2015 at 5:20 PM, elky <mansell...@gmail.com> wrote:

> Hi everyone,
>
> I reworked my previous attempt
> <https://github.com/django/django/pull/4232> of stylizing django admin
> and now it looks more like original in terms of color scheme. See
> attachments.
>
> For those who want to play with new theme I created an app which is *very*
> simple to install, see here: https://github.com/elky/django-flat-theme.
> Feel free to criticize - I'll appreciate any feedback.
>
> Thank you
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" 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/da28de40-82b4-44e3-875d-1b18f930704e%40googlegroups.com
> <https://groups.google.com/d/msgid/django-developers/da28de40-82b4-44e3-875d-1b18f930704e%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> 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  (Contributions to Django itself)" 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%3DJzJC%2BSFhY9_-KMj_Ze7yi-hiGbLhCJ2puJgOt74r9V4dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Optional schemes in URLValidator causes backward incompatible changes

[Bruno Ribeiro da Silva]

Thanks! It's open: https://code.djangoproject.com/ticket/23985

On Fri, Dec 12, 2014 at 12:12 PM, Michael Manfre <mman...@gmail.com> wrote:

> Please open a ticket for this.
>
> On Fri, Dec 12, 2014 at 9:11 AM, Bruno Ribeiro da Silva <
> bruno.dev...@gmail.com> wrote:
>
>> Hey everyone,
>>
>> I just found out that the new schemes option of URLValidator causes
>> incompatible changes for people who were using custom regex to restrict
>> schemes. Could somebody put a note in Django 1.7 backward incompatible
>> changes documentation? Should I open a ticket for this?
>>
>> Thanks!
>>
>> --
>> Bruno Ribeiro da Silva
>> Python Dev and Homebrewer!
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django developers (Contributions to Django itself)" 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%3DJyajyKdvJ6-0oK%3D7NTt4fkpcOkFU8U9r9B8dQO9ob%3D7KA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/django-developers/CAE-2%3DJyajyKdvJ6-0oK%3D7NTt4fkpcOkFU8U9r9B8dQO9ob%3D7KA%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" 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/CAGdCwBvt3VKvpkkGYKwWJZO%3D_4irF4LuJV3Th5G_vBFiNJcFOQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/django-developers/CAGdCwBvt3VKvpkkGYKwWJZO%3D_4irF4LuJV3Th5G_vBFiNJcFOQ%40mail.gmail.com?utm_medium=email_source=footer>
> .
> 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  (Contributions to Django itself)" 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%3DJyorY7gTn%2BWbLhEqF4%2BGyS4ibm69SLndTSQ4yxmJV0JOw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Optional schemes in URLValidator causes backward incompatible changes

[Bruno Ribeiro da Silva]

Hey everyone,

I just found out that the new schemes option of URLValidator causes
incompatible changes for people who were using custom regex to restrict
schemes. Could somebody put a note in Django 1.7 backward incompatible
changes documentation? Should I open a ticket for this?

Thanks!

-- 
Bruno Ribeiro da Silva
Python Dev and Homebrewer!

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" 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%3DJyajyKdvJ6-0oK%3D7NTt4fkpcOkFU8U9r9B8dQO9ob%3D7KA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Built-in support for Jinja2 in Django

[Bruno Ribeiro da Silva]

I think it's an awesome idea to have a pluggable template engine
architecture in Django. I hope you can stretch the goal to have the second
step (djando templates as a library) done too!
On Oct 2, 2014 8:48 AM, "Gwildor Sok"  wrote:

> It's good to see something happening after the lengthy discussion of last
> February on this mailing list. Thank you for taking initiative in this. I
> believe this will be a great addition to make Django even better.
>
> On Thursday, October 2, 2014 1:28:01 AM UTC+2, Russell Keith-Magee wrote:
>>
>>
>> On Thu, Oct 2, 2014 at 3:04 AM, Aymeric Augustin > polytechnique.org> wrote:
>>
>>> Hello,
>>>
>>> I've been thinking about providing built-in support for Jinja2 in
>>> Django. I found that supporting pluggable template engines, like Django
>>> does for databases, caches, etc. would be the most elegant solution. The
>>> best summary I have at this time is on the crowdfunding campaign's page:
>>> http://igg.me/at/mtefd.
>>>
>>> I will submit a detailed proposal to this mailing-list as soon as I have
>>> a sufficiently good version. Until then, if you hear noises, don't worry --
>>> there will be a technical discussion here before any decision.
>>>
>>
>> SHUT UP AND TAKE MY MONEY!!!1!1!BBQ!
>>
>> Seriously - thanks for taking this on. It's yet another of those huge
>> projects with huge potential impact that you seem to excel in tackling.
>> Can't wait to see the results!
>>
>> Yours,
>> Russ Magee %-)
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" 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/ce7956c7-2ae6-4b95-aa1e-539cb81c3267%40googlegroups.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  (Contributions to Django itself)" 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%3DJw0HRn21dBAJ%2BHQ9kooMwwX-ENyJ30vYDdW%2BuyawuWEQA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANNOUNCE] Django 1.7 released

[Bruno Ribeiro da Silva]

That's good news!
On Sep 2, 2014 7:13 PM, "James Bennett"  wrote:

> Django 1.7 is now available:
>
> https://www.djangoproject.com/weblog/2014/sep/02/release-17-final/
>
> Alongside this are bugfix releases for 1.4, 1.5 and 1.6. The bugfix 1.5
> release is the final releae in the 1.5 series, as Django 1.5 has now
> reached end-of-life.
>
> --
> 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/CAL13Cg_Cdzf3aYLxfV0qgrMY3CqbOqt%3D0DxEm1V27%2BzF65O_cA%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/CAE-2%3DJw%3D_ZN0RzJEgo-eC5RxMAK%3DEE-0FpqPGgf-fm9%2BYG6v1A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Who manages the django-i18n mailing group?

[Bruno Ribeiro da Silva]

Hey folks,

Django now 100% translated to pt_BR.

Thanks for the help with transifex!


On Thu, Apr 10, 2014 at 9:58 AM, Bruno Ribeiro da Silva <
bruno.dev...@gmail.com> wrote:

> Thank you!
>
>
> On Thu, Apr 10, 2014 at 9:49 AM, Ramiro Morales <cra...@gmail.com> wrote:
>
>> On Thu, Apr 10, 2014 at 9:26 AM, Bruno Ribeiro da Silva
>> <bruno.dev...@gmail.com> wrote:
>> > Hi everyone,
>> >
>> > I'm trying to fix some translations in transifex but I'm waiting for 3
>> days
>> > since I requested to join the pt-br group.
>>
>> I've just accepted you there (with my Transifex the Django project admin
>> hat.)
>>
>>
>> --
>> Ramiro Morales
>> @ramiromorales
>>
>> --
>> 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/CAO7PdF_6rwNWFTh6rpJw9MzvFuCxMN5i5WVW0AHpbaa6eX8uOQ%40mail.gmail.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Bruno Ribeiro da Silva
> Python Dev and Homebrewer!
>



-- 
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%3DJytFt780RvOfLY1OjUBcB08oJnX75A6oUU_SXX-0k81cg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Who manages the django-i18n mailing group?

[Bruno Ribeiro da Silva]

Thank you!


On Thu, Apr 10, 2014 at 9:49 AM, Ramiro Morales <cra...@gmail.com> wrote:

> On Thu, Apr 10, 2014 at 9:26 AM, Bruno Ribeiro da Silva
> <bruno.dev...@gmail.com> wrote:
> > Hi everyone,
> >
> > I'm trying to fix some translations in transifex but I'm waiting for 3
> days
> > since I requested to join the pt-br group.
>
> I've just accepted you there (with my Transifex the Django project admin
> hat.)
>
>
> --
> Ramiro Morales
> @ramiromorales
>
> --
> 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/CAO7PdF_6rwNWFTh6rpJw9MzvFuCxMN5i5WVW0AHpbaa6eX8uOQ%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%3DJyPU-WiyZJygrPwOdZ6OiJ%3DMTfYxCREFMJ2JQmJkYFW5A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Who manages the django-i18n mailing group?

[Bruno Ribeiro da Silva]

Hi everyone,

I'm trying to fix some translations in transifex but I'm waiting for 3 days
since I requested to join the pt-br group. I already sent two messages to
django-i18n and none was approved. Looking at the list, the last message is
from Feb 24. Can someone give me some help here? I would like to do this
before the the window for translation closes.

Thanks!

-- 
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%3DJwF00DAZGN%3DPOs%3Dspkax_5Mu8a-W9TS-Goa6QiaH_MQEw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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 <armorsmit...@gmail.com>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<https://groups.google.com/d/msgid/django-developers/CAE-2%3DJyri-hr-Q9%2BzdezBxkLG2-qzViBQmF9bwotmPFBvZ%3DS%3Dg%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> 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<https://groups.google.com/d/msgid/django-developers/CA%2By5TLZFRmb2x0r%2Bwjk3GJXaiAyddUZ_X_auRg%3Dq2RBQqZvXCQ%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> 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.

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: AbstractUser to get more abstract

[Bruno Ribeiro da Silva]

derstand correctly), if you install the auth app,
>> you get the Group and Permission models (and supporting code, natch), as
>> well as the User model. If you decide to set a different User model using
>> AUTH_USER_MODEL, but you keep auth installed for these other aspects
>> (Group, Permission, etc.) then Django installs an auth_user table that
>> isn't used (note to self: verify this).
>>
>> If you set AUTH_USER_MODEL to something other than auth.User, you are
>> making a statement that you *do not want* the stock model. This is true
>> whether you change it to the upcoming, included "EmailUser" model, or to
>> something else entirely.
>>
>> So, I don't think that option 2 "makes a special case of one particular
>> extension user". If anything, I assert it would do the opposite: it
>> actually performs the most expected behavior in all cases. If the plain
>> User model is the AUTH_USER_MODEL and d.c.auth is in INSTALLED APPS, then
>> it is installed. If you choose to use an included-in-core e-mail model and
>> install d.c.auth, you get that model and table *instead of* the current
>> User model. And, if you use your own, special custom User model, but
>> install auth for the remaining aspects, then you get your custom user
>> model, and not either of the stock ones.
>>
>> Basically, my understanding is that you start to get unclean and
>> counter-intuitive behavior when you want to install the auth app for
>> everything other than the User model (and forms, etc.), that this would
>> correct.
>>
>> Best Regards,
>> Luke
>>
>> P. S. To be clear, I am not trying in any way to be argumentative, and I
>> am happy to implement the separate app if that is what the core developers
>> decide on.
>>
>> --
>> 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.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>> --
>> 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.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
> --
> 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.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>  --
> 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.
> For more options, visit https://groups.google.com/groups/opt_out.
>



-- 
Bruno Ribeiro da Silva
Python/Django/Java Developer
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.
For more options, visit https://groups.google.com/groups/opt_out.