PyCharm not stopping at breakpoint

HI All, I have some unit tests (using django-nose). As one was failing I wanted to debug the test (to see what's going on), but pyCharm does not stop at the breakpoint. I'm working with Python 2.7.6, Django 1.5.1, django-node 1.2, nose 1.3.3. PyCharm 4.5.3 Do you have any ideas? Thanks Regards

Re: PyCharm not stopping at breakpoint

Hi, are you sure that the breakpoint is reached? Maybe the test fails before that? Also, you might want to update your PyCharm, as it is quite a few versions behind :) Best, Žan Dne ponedeljek, 18. april 2016 15.04.56 UTC+2 je oseba scha...@gmail.com napisala: > > HI All, > I have some unit

request user

Good afternoon people, I am using django material, LayoutMixin My view is: class NewProfissoesPessoaView (LoginRequiredMixin, LayoutMixin, extra_views.NamedFormsetsMixin, extra_views.CreateWithInlinesView): title = "New Job" model = ProfissoesPesso

recuperar user logado

Boa tarde pessoal, Estou utilizando django material, LayoutMixin Minha View é a seguinte: class NewProfissoesPessoaView(LoginRequiredMixin,LayoutMixin, extra_views.NamedFormsetsMixin, extra_views.CreateWithInlinesView): title = "Nova Profissão" mod

My Form is not persisted

Helo everybody. Could someone answer me this question on stackoverflow? http://stackoverflow.com/questions/36703456/django-my-form-isnt-persisting-on-database -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and st

Re: Migrations force me to have, forever, any name/reference I use in field validators=, choices=, whatever, valid forever (even if the requirements change).

On Friday, February 27, 2015 at 11:22:13 PM UTC+1, Gergely Polonkai wrote: > > Hello, > > another solution may be to patch your models in the migration module or > class > The best solution is not to use Django built-in migrations. Of course you can create them very quickly (via automatic "ma

Re: PyCharm not stopping at breakpoint

Schaf, Yes, I've seen that.  In my case, it's not a bug.  It's an intentional design decision that is necessary for a symbolic debugger to work the way you want it to.  Happens in all symbolic debuggers, including PyCharm. Here's a explanation I sent m

No Downtime Code Releases

Hey, I have two issues I'm looking at solving at work, and I'm looking for a couple suggestions as to how other people have solved this. The two things are: * scale out their django installation to allow for smaller releases (I'm thinking microservices, but it could also be internal django ap