Also, well, I mean... If there's all that time/effort involved... Just get yourself some tea, coffee, doodle on some piece of paper, do some push-ups, some yoga, prey, meditate, breathe and then... Code, lol!
So, actually, on the museum's ticketing site they say that the internet tickets are sold out, but if you actually get there, there's a limited amount of tickets that are sold each day (because not everyone uses the internet) : "Merci de noter que des places pour la visite le jour même sont en vente chaque jour directement à l'accueil de l'exposition, dans la limite des places disponibles.".
Well, as previously stated in Pycharm and Visual Studio (not tested on others) there is. If I remember correctly, both will install their requirements remotely and then allow you to do so. However, I would not recommend it:
- you will probably forget to clean up after the fact leaving you with both performance and security problems
- you should never debug in production, use something like Sentry instead also, better to replicate the production environment in a sandbox (either on your machine using Vagrant or Docker, etc. if feasible) or in the cloud by taking a snapshot of your production environment and using it as a sandbox to debug (and then of course destroying it after use).
Not trolling, but what's wrong with visual remote debugging using either Pycharm or Visual Studio? I find it much more rich information wise than using pdb.
Yes, you can. It has to be where there is templating language of course (you cannot put a breakpoint on a arbitrary div for example), you can also debug the rendering of the template through Pycharm if you want to in order to have a full stack debug, but I'm used to doing that using the browser developer tools.
Right, no one wants to work on a 10k line view.py file. However, if you put everything into its own app, like I did, then you run into circular dependencies as your project gets closer to feature complete. So, the answer is somewhere in the middle. At the moment, I have about 20 apps, with 1 to 4 models per app, and 20% of all that is highly interdependent. I should have put the big, highly interdependent pieces in one app, and have the less connected pieces in separate, bare-bones crud-apps.
reply