Re: Using auth stuff without installing the auth app
On 23 Mar 2016, at 01:57, Matt wrote:
> I like to use the authentication machinery in Django, without explicitly
> putting 'django.contrib.auth' in INSTALLED_APPS. This prevents a bunch of
> unused tables from being creating in the database.
Hello,
For the record, we came to the following resolution on the related Trac ticket:
MIGRATION_MODULES = {
'auth': None
}
This trick also works for django.contrib.sessions if you don’t use the database
or cached database backend.
--
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.
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/461E0A12-4F1B-4A41-8800-CB4B4283D7FB%40polytechnique.org.
For more options, visit https://groups.google.com/d/optout.
Re: Django Box - A vagrant virtual machine for testing Django
Hi Josh, This looks very promising. Thanks for making it. On Sunday 28 August 2016 08:55:05 Josh Smeaton wrote: > > *1. Should we host the django-box project under the django organisation?* > > [...] Should this project be proposed for inclusion within the django > organisation under DEP7 > https://github.com/django/deps/blob/master/final/0007-official-projects.rst > if consensus leads us to leaving it within the django organisation? > I think yes on both counts (host under Django and DEP7), but see below. > *2. Where should we host the final box image?* > Sorry, I am not experienced enough with vagrant and its ecosystem to form an opinion. > > Finally, I'd just like to try and gauge the interest in this project. > [...] Would you use this? > I have my environment set up already, and I suspect this would hold for a lot of the more experienced developers here; do you think the new box will improve things for me? On a different angle -- is the intention to have this box set up to ease testing of django apps? Even if the answer to both above questions is "no", I suppose it will make it easier to make the first contributions; this is enough, IMO, to justify DEP7 inclusion. Have fun, Shai.
Sonar for the Django rpoject
Hi guys, I am new to Django and I want to contribute to the project soon. Sorry for the question if it's not appropriate. Do you consider using SonarQube (or something similar) for code quality analysis? Regards, Ivan -- 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/59b969d1-4175-4fe8-836c-8e4a55dcb22d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Sonar for the Django rpoject
On 28 Aug 2016, at 20:46, Ivan Sevastoyanov wrote: > Do you consider using SonarQube (or something similar) for code quality > analysis? Hello Ivan, Generally speaking, there isn’t a lot of demand for code changes with no impact on functionality, especially as first time contributions. Such patches are tedious to review compared to the value they add. In practice it can be faster for a committer to redo the job that to check that it was done correctly. The coding style tends to improve as a side effect of making other changes in an area. If SonarQube goes beyond traditional code quality guidelines, for example if it does static analysis and can find bugs with reasonable accuracy, that would be more interesting. In that case you’ll have to tell us a bit more about the kind of results you expect. Many people (including myself) have never heard of SonarQube before and aren’t familiar with what it can do. I hope this helps, -- Aymeric. PS: could you pick a better word than “guys” to address people on this mailing list? Even though “guys” can include people regardless of gender in some cultures, originally “guy” is a synonym for “man”, and you don’t want to imply that you’re only talking to men. Thanks! -- 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/AF09D0DA-C80C-4589-AAA1-C2208141B4DF%40polytechnique.org. For more options, visit https://groups.google.com/d/optout.
Re: Sonar for the Django rpoject
My mistake. I had to ask with more details. My question is do you consider using SonarQube for code quality analysis, static analysis and find bugs because it's able to do that. I am asking for the Django project as a whole. Sonar can track the commits and show you if there are added some "code smells". That way we can prioritize some of the findings for fixing in the next releases. PS: I accept the criticism and won't use guys annymore :) Regards, Ivan On Sunday, August 28, 2016 at 10:23:02 PM UTC+3, Aymeric Augustin wrote: > > On 28 Aug 2016, at 20:46, Ivan Sevastoyanov > wrote: > > > Do you consider using SonarQube (or something similar) for code quality > analysis? > > > > Hello Ivan, > > Generally speaking, there isn’t a lot of demand for code changes with no > impact on functionality, especially as first time contributions. Such > patches are tedious to review compared to the value they add. In practice > it can be faster for a committer to redo the job that to check that it was > done correctly. The coding style tends to improve as a side effect of > making other changes in an area. > > If SonarQube goes beyond traditional code quality guidelines, for example > if it does static analysis and can find bugs with reasonable accuracy, that > would be more interesting. In that case you’ll have to tell us a bit more > about the kind of results you expect. Many people (including myself) have > never heard of SonarQube before and aren’t familiar with what it can do. > > I hope this helps, > > -- > Aymeric. > > PS: could you pick a better word than “guys” to address people on this > mailing list? Even though “guys” can include people regardless of gender in > some cultures, originally “guy” is a synonym for “man”, and you don’t want > to imply that you’re only talking to men. Thanks! > > -- 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/c8163c17-d163-4320-bf84-9019aaab654e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Sonar for the Django rpoject
On 28 Aug 2016, at 21:43, Ivan Sevastoyanov wrote: > My question is do you consider using SonarQube for code quality analysis, > static analysis and find bugs because it's able to do that. I guess that depends on the signal / noise ratio in the things SonarQube flags. Perhaps you could do an initial run and see whether SonarQube spots interesting bugs? I have no idea what the results could be because I’m not familiar with static analysis of Python code. -- 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. 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/C39CB625-36D8-4194-8630-29BC4B3CC620%40polytechnique.org. For more options, visit https://groups.google.com/d/optout.
Re: Sonar for the Django rpoject
OK, I will try to do that on my machine and will post the results here (because frankly speaking I haven't done it before on my own). I don't know when I will have enough time to do it but I guess 3 to 4 days. Regards, Ivan On Sunday, August 28, 2016 at 11:16:57 PM UTC+3, Aymeric Augustin wrote: > > On 28 Aug 2016, at 21:43, Ivan Sevastoyanov > wrote: > > > My question is do you consider using SonarQube for code quality > analysis, static analysis and find bugs because it's able to do that. > > > I guess that depends on the signal / noise ratio in the things SonarQube > flags. > > Perhaps you could do an initial run and see whether SonarQube spots > interesting bugs? > > I have no idea what the results could be because I’m not familiar with > static analysis of Python code. > > -- > 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. 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/409391dd-3643-4ef7-8b32-5f0f92e2b738%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Django Box - A vagrant virtual machine for testing Django
> > I have my environment set up already, and I suspect this would hold for a > lot > of the more experienced developers here; do you think the new box will > improve > things for me? > > It probably won't make a big difference for those that already have environments setup for django development, but it'll definitely ease the process for newer contributors. Where it will benefit those of us who already have environments setup is when django deprecates older databases or libraries, so that you'll always be able to have a newer environment without manually going through and upgrading existing components. The commands for running flake8/isort/spelling would help with discovery unless you've already transitioned to running them with the new tox configuration. > On a different angle -- is the intention to have this box set up to ease > testing of django apps? > > Not really, no, but that doesn't mean it can't be used for that purpose. All that's required is a new synced_folder declaration within the Vagrantfile that'd mount a users project within the virtual machine, and then they can link to the existing settings modules to run their tests against the various databases. I guess this would be more useful for library developers rather than regular projects. For more advanced projects that want to use vagrant for development, they could include their own Vagrantfile that uses the django-box as a base from which to build upon. Thanks for the feedback. -- 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/4f98d6c0-a7bc-4dce-bbdd-675fe8adb388%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Django Box - A vagrant virtual machine for testing Django
An interesting idea put forward by Ed Morley on the issues tracker (https://github.com/django/django-box/issues/12) is to merge the django-box project into the django main repository directly. The meat of the suggestion is copied below: > The ideal end state I see is that this project lives in the main django > repo. That way (regardless of compiled box vs build locally) people just > have to: > >- git clone django repo > > >- install virtualbox/vagrant > > >- vagrant up > > ...with no added complication of having to clone a second repo and put it > in the correct location. I like the idea in principle, but I realise it'd add a non trivial burden to the existing django project for what is an unproven project. Still, if I'm already soliciting feedback it's worth asking about this too :) Cheers -- 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/c61b4f06-ca2e-448a-9dd7-a5660bfc8033%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
