Re: extra files in startproject
Alex Ogier writes: > That seems like too much to ask. "setup.py install" should Just > Work(tm), In the absence of a proper package management system (as implemented in operating systems that solved this problem decades ago), you can't expect it to Just Work. Parallel installation of multiple versions, detection of previous versions, upgrade and uninstallation, dependency management – these are problems solved by a package manager, and ‘setup.py’ doesn't play well with them. Python's ‘setup.py’ can't be expected to do the job of a package manager, especially not in parallel to the OS which often has its own package manager. -- \ “For fast acting relief, try slowing down.” —Jane Wagner, via | `\ Lily Tomlin | _o__) | Ben Finney -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Re: does django-admin need a man page?
Tim Graham writes: > I'd like to remove it though (or make it point people to 'django-admin > --help') as it's out-of-date and 'django-admin --help' provides the > same information in a much easier to maintain format. Does anyone else > have input on this? Man pages are a standard interface on Unix, and it's very helpful to keep the man page up to date for any command available at the command line. Certainly when I'm in my IDE it's much better to be able to query the manpage database for a command, than to figure out whatever idiosyncratic help system it prefers me to use. -- \“Most people, I think, don't even know what a rootkit is, so | `\ why should they care about it?” —Thomas Hesse, Sony BMG, 2006 | _o__) | Ben Finney -- 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/85lhn0xfkl.fsf%40benfinney.id.au. For more options, visit https://groups.google.com/d/optout.
Re: Featurereuqest: Helpfull tracebacks
Roland van Laar writes:
> I would like to know which Model and Field caused the error.
>
> Such as: DatabaseError: own_app.models.User.street: value too long for
> type character varying(100).
This could be done by having Django's database interface catch the
error, and chain a new exception from that one:
try:
pgsql_cursor.execute(foo)
except pgsql.SpamException as exc:
error = DatabaseError(
"in {model_name}: {exc}".format(
exc=exc, model_name=fully_qualified_model_name))
raise error from exc
See PEP 3134 for the exception chaning syntax ‘raise foo from bar’
http://www.python.org/dev/peps/pep-3134/> which is now in Python
http://docs.python.org/3/library/exceptions.html>.
--
\ “I do not believe in forgiveness as it is preached by the |
`\church. We do not need the forgiveness of God, but of each |
_o__)other and of ourselves.” —Robert G. Ingersoll |
Ben Finney
--
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.
Re: Featurereuqest: Helpfull tracebacks
Florian Apolloner writes: > On Thursday, August 22, 2013 6:43:39 AM UTC+2, Ben Finney wrote: > > > > This could be done by having Django's database interface catch the > > error, and chain a new exception from that one: > > Knowing the model alone is imo pretty useless since that's in the > traceback anyways I didn't see a traceback. The OP gave only the error message. How do you know they are getting the model name? > also what you suggest has to happen way up higher the chain; otherwise > model wouldn't be known… Exactly. Catch the low-level error from the database engine at a point where the model is known. Then chain a new, more-informative exception, which will say what the fully-qualified model name is, along with the full exception information of the original exception. -- \ “Once consumers can no longer get free music, they will have to | `\buy the music in the formats we choose to put out.” —Steve | _o__) Heckler, VP of Sony Music, 2001 | Ben Finney -- 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.
Re: Requiring GitHub login for actions on Trac
Aymeric Augustin writes: > In order to fix the spam problem while maintaining an easy workflow, > I'm proposing to require GitHub auth for all "write" operations: > creating a ticket, adding a comment, etc. Most people interested in > Trac should have a GitHub account already. −1. I am happy to agree to Django's BTS terms of use, not GitHub's. Please don't make the former depend on the latter. -- \ “Isn't it enough to see that a garden is beautiful without | `\ having to believe that there are fairies at the bottom of it | _o__) too?” —Douglas Adams | Ben Finney -- 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/85y4v19ljh.fsf%40benfinney.id.au. For more options, visit https://groups.google.com/d/optout.
Re: Requiring GitHub login for actions on Trac
Alex Gaynor writes: > For new users, being able to reuse existing authentication credentials > is a considerable step up Agreed. This is an argument to allow OAuth login. It is not an argument to privilege any OAuth provider over others, or any OAuth provider over no provider at all. > I regularly give up on filing bug reports against other OSS projects > because I'm frankly too tired to register for > yet-another-JIRA-instance. Likewise, I regularly give up because too much dependence is given to Facebook, or GitHub, or etc. etc. etc. Please don't make a new user's use of one service depend on them having agreed to a specific unrelated corporation's terms of use. They should be free to join whether or not they are a user of GitHub or Facebook or Twitter or JoesOwnProvider or none of the above. -- \“If I melt dry ice, can I swim without getting wet?” —Steven | `\Wright | _o__) | Ben Finney -- 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/85tx5p9jtb.fsf%40benfinney.id.au. For more options, visit https://groups.google.com/d/optout.
Re: Requiring GitHub login for actions on Trac
Aymeric Augustin writes: > GitHub doesn't require creating a new account, since anyone interested > in contributing to Django should have a GitHub account already to > submit pull requests. This seems to be a common assumption, but it's not true — unless you only count VCS contributions. Are we not talking about contributors to Django's Trac instance, though? There is currently no need to have a GitHub account to contribute there, and you're proposing to require that. > But don't ask me to keep deleting spam manually. I don't want that to continue. I also don't want these two issues to be tied together. -- \ “Facts are stubborn things; and whatever may be our wishes, our | `\ inclinations, or the dictates of our passion, they cannot alter | _o__)the state of facts and evidence.” —John Adams, 1770-12-04 | Ben Finney -- 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/85a97fap9o.fsf%40benfinney.id.au. For more options, visit https://groups.google.com/d/optout.
Re: Requiring GitHub login for actions on Trac
Aymeric Augustin writes: > You're right. Then just remove "to submit pull requests" from my > argument and it still holds, simply because the vast majority of the > Django ecosystem is on GitHub, and you can't participate meaningfully > without GitHub. You can, at present, participate in Django's bug tracker without a GitHub account. The bug tracker contributions don't count, then? You consider participation in bug tracker discussions to be meaningless? -- \ “For every complex problem, there is a solution that is simple, | `\ neat, and wrong.” —Henry L. Mencken | _o__) | Ben Finney -- 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/85zjff8o84.fsf%40benfinney.id.au. For more options, visit https://groups.google.com/d/optout.
Re: Requiring GitHub login for actions on Trac
Aymeric Augustin writes: > Contributors who refuse GitHub's ToS can participate on Trac again. For working to fix this, and for acknowledging these people are contributors: Thank you! -- \ “Truth is stranger than fiction, but it is because fiction is | `\ obliged to stick to possibilities, truth isn't.” —Mark Twain, | _o__) _Following the Equator_ | Ben Finney -- 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/8538clzmv8.fsf%40benfinney.id.au. For more options, visit https://groups.google.com/d/optout.
