On Fri, Feb 20, 2015 at 9:29 AM, Diana Probst
wrote:
> The last time I logged into GitHub was at least one computer ago. And
> that computer blew up a bit. I'll try to get on, but this is contingent on
> many factors, and I don't have control over them all. What I
The last time I logged into GitHub was at least one computer ago. And that
computer blew up a bit. I'll try to get on, but this is contingent on many
factors, and I don't have control over them all. What I will do is read the
docs on contributing.
Thanks for the time, both/all of you.
Diana,
I've been working on my own first patches to Django. I'm available all day
tomorrow from about 8-5:30 CST if you want any help with the basic steps.
You'll basically want to fork django/django, git clone that to your local
machine, and set the original repo as your upstream remote to
On 20 February 2015 at 11:49, Diana Probst
wrote:
> Never done either of those things, and I'm completely not set up to do
> them. I will if creating this subject has made me the owner of it, but
> it's a lot more work for me than it would be for someone else. I'd
Never done either of those things, and I'm completely not set up to do them. I
will if creating this subject has made me the owner of it, but it's a lot more
work for me than it would be for someone else. I'd start with the Writing your
First Django Patch part of the tutorial, yes?
Thanks
In all cases in Django, if your code imports the class, you can put it
wherever you like - so long as Python can find it. It's only things that
are "discovered" by Django [admin, models, etc] that must be in a specific
module.
By convention, forms are put into forms.py ... but that's so _humans_
I've been struggling to add forms to an app I am building, because the
context of where to put form classes is missing in the docs. I don't want
to take a guess, even if it's right, when I could be following best
practice. In the 1.7 tutorial, the namespacing and file naming is laid out
On Thu, Jan 22, 2015 at 12:32 PM, Andreas Kahnert
wrote:
> Hi again,
> Well, I can acknoledge that your reasons for list (beginner friendly) are as
> good as my reasons for tuples (seems to be more logical choice for things
> that are static). To say it in other words,