Re: Introduction & Contribution Interest – Django

Hi, I'm new to Django. When I try to generate a login token, I receive these errors: json CopyEdit {"detail": "Authentication credentials were not provided."} {"error_short": "Module is not Assigned", "status": "failed"} Any help resolving these issues would be appreciated. Thanks! On Saturda

Hi everyone I am the beginner django back end developer.

while working inside the project I getting the error for generating the token. the error was shown { "detail": "Authentication credentials were not provided." } how to fix this error to get the token from the login api of the website -- You received this message because you are subscribed t

Re: Proposal to upgrade django.core.mail to Python's modern email API

Adding my support for the suggested approach. Start small and central and step-by-step. 👍 > (I'm going to add a link in django-anymail's "you probably don't need proprietary ESP templates " docs.) Thanks! Much appreciated! And thx on your

Re: Proposal to upgrade django.core.mail to Python's modern email API

Hi all! Jakob Rief pointed this discussion out to me. I've been going around lately to make some advertisement for my idea of class-based emails. I've implemented a package called "django-pony-express" which in a nutshell provides to things: * A class-based way of creating new emails (very sim

Re: Need teamwork to gain experience!

Add me also On Tue, 20 Jun 2023 at 16:05, Eva Kemo wrote: > add me as well https://github.com/kemoeverlyne > > On Tue, Jun 20, 2023 at 4:04 PM ADEDIRAN ISAAC > wrote: > >> Please add me as well, >> https://github.com/aiziks >> >> On Mon, Jun 19, 2023, 6:54 PM web_dj wrote: >> >>> You are welco

How to Get Started with Contribution

Respected Sir/Madam, I am V Krishnasubramaniam, a Third Year undergraduate student in Mumbai University. My proficiency in technical skills are as follows: Languages: Java, Python, C, HTML, CSS, Javascript, PHP, SQL Frameworks: Laravel, Flask, Swing, Hibernate ORM, Maven DevOps: Docker

Re: Infinite scrolling, Ajax, Phone or PC?

Simple: jQuery.scroll(infinite=true.null).django(); On Sunday, April 1, 2018 at 10:55:31 AM UTC-4, Jamaldin Pro wrote: > >Hello. > >How can I make Infinite scrolling html? example: > https://www.megacom.kg/hype/ru.html#instruction >How can I go from first url to another without reloa

Re: Google Summer of Code 2017

decisions, commenting on the ticket you > intend to work on might also be appropriate. > > On Friday, February 3, 2017 at 7:16:48 AM UTC-5, HITESH V. BHAGCHANDANI > wrote: >> >> My college blocks ports for IRC and am unable to communicate freely with >> the django commu

Re: Google Summer of Code 2017

My college blocks ports for IRC and am unable to communicate freely with the django community. By the way, I have joined only a few days ago and would like to know where I can post my queries regarding details( which function to use, what file to edit and so on) about any patch that I'd be writ

how to deal with a multi-schema legacy database?

Hi, I'm a newbie with Django and I need some advice about legacy database. I've got a PostgreSQL database (8.4) with several schemas, each containing a lot of tables. And I wish to transfer the actual associates site into Django, but it would take to much time to re-organise all the database.

Doc idea: Split request & response?

The request & response docs for 1.3 look like: Reference: Request/response objects | TemplateResponse objects The first link has requests, associated request objects, and responses. The second link has new derived response objects. What does anyone think about reorganizing this to: Refer

Remove admonition in admin docs?

Since older "versionadded/changed" tags were dropped in 1.3, should the admonition mentioning 0.96 on top of the admin docs also be dropped? "The admin site has been refactored significantly since Django 0.96." http://docs.djangoproject.com/en/dev/ref/contrib/admin/ If so, I have a doc patch

Style guide for section headers in docs?

The Django docs prefer "First word only" capitalization, though there are some cases where seemingly random words are also capitlized, "Views" in a couple headers here for instance: http://docs.djangoproject.com/en/dev/topics/http/views/ Just checking that "First word only" (and also class names a

Documentation style guide hint for section headers?

The docs seem a bit inconsistent on the use of raw lines for headings that describe classes/methods/attributes. The stated preference is to use a directive before the heading to make it easier to link. Is there also a preference on whether these headings should be raw quoted or normal text? FWIW,

Re: extra_context in all admin views?

For what it's worth, there are several existing tickets on this subject: * http://code.djangoproject.com/ticket/5298 * http://code.djangoproject.com/ticket/8670 * http://code.djangoproject.com/ticket/12044 -- You received this message because you are subscribed to the Google Groups "Django deve

Re: Admin patches

I have a pending admin patch too: http://code.djangoproject.com/ticket/11651 (With tests and docs, though probably needs some better function names.) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to djang

Re: django-3k

> It can now convert and start the test suite, however, this doesn't > produce any results, yet. Following up to myself: it now does run the test suite to completion: Ran 1425 tests in 384.689s FAILED (failures=222, errors=539) If you are curious what the failures and errors are, just run it fo

django-3k

I have now published my 3.x port on bitbucket, at http://bitbucket.org/loewis/django-3k/ It can now convert and start the test suite, however, this doesn't produce any results, yet. Feel free to use the bitbucket issue tracker to report problems or contribute changes. Regards, Martin -- You r

Re: Porting Django to Python 3

> Some examples: Thanks for posting them: > >>> Template(u"{{ foo }}").render(Context({"foo":"bar"})) > u'bar' I get py> Template("{{ foo }}").render(Context({b"foo":b"bar"})) '' I think that's correct: the dictionary has no key "foo". I'm also unsure what this has to do with UTF-8: isn't this

Re: Porting Django to Python 3

> > In many cases, this is true, but there are other scenarios (certain > > forms of exception handling, for example) where there is no syntax > > that's valid in both versions. That's syntax, not just libraries and > > functions. There's no way to even get a file to parse in both Python 2 > > and

Re: Enhanced debug output colors: django code is green, user code is red.

ngo color, so I can note DB related problems easier. That probably opens up a big configuration can of worms; I haven't had the time yet to code up a patch myself. - Adam V. http://adamv.com On Nov 3, 9:33 am, Waylan Limberg wrote: > On Tue, Nov 3, 2009 at 10:57 AM, Tobias McNulty >

Re: Brand new projects should pass their tests (the django.contrib.auth thing from #7611)

In a Django project, I have a bash script that does: APPS=`python -c "import settings; print settings.only_our_apps()"` ./manage.py test $APPS In settings.py I define OUR_APPS as a list, and then define INSTALLED_APPS as the django built-ins plus OUR_APPS: _OUR_APPS = ( 'something', 'an

Re: ImageField performance

I fully understand the convenience of being able to read just the header. (it's ok if it doesn't go in the sources) I'm wondering, could it be possible to adapt the loop to read bigger chunks maybe. Nevertheless, in my case, the 35 meg is a TIFF file, while a 10 meg file that is also very slow is

Re: Py3k port updated

> I'll give it a go, but for someone who doesn't know about running 2to3 > etc, to make things a but more obvious can you add to your page a > quick set of instructions as to what someone needs to do to try this > out. Ie., what needs to be done after a checkout, does one apply patch > and then in

Re: Py3k port updated

> Have you by chance tried running it on top of Apache/mod_wsgi (version > from subversion which has Python 3.0 support)? No, only in runserver mode. Regards, Martin --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups

Re: Py3k port updated

> Did you by any chance try running the Django test suite(because that's > probably going to be the best way to spot breakages). No, I haven't (or only to the degree to find out that runtest.py is not in 3.0 syntax, as it uses incorrect except clauses). I'm fairly certain though that the test sui

Py3k port updated

I have updated my Py3k port of django. As before, it is just the bare minimum to get through the tutorial; as the possibly most significant change since the previous patch, it now supports psycopg2. I have updated the Wiki page at http://wiki.python.org/moin/PortingDjangoTo3k with the new patch.

Re: MS SQL backend as a proper external backend (was: RFC: Django 1.0 roadmap and timeline)

> To solve it I proposed[1] another strategy: delegate type conversion to the > backend. +1 I maintain the external django-mssql backend, and I would HUGELY prefer to get "real Python types" instead of to-string types for things like dates/times/decimal/etc. (Converting everything to strings "f

Re: Backend-specific DateTimeField pre-processing

> I think that it's perfectly OK to distribute a patch to change the > hardcoded functionality -- it's far better than trying to monkey-patch > the code under active development. I have a patch in my backend already, to enable regex searches in MS SQL. I think this is reasonable, as you have to i

Backend-specific DateTimeField pre-processing

is that gross? Or is there a better way to handle this that I'm missing? (Or do I just have to suck it up in my backend?) - Adam V. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django develope

Re: Re: Porting Django to Python 3.0 as a GSoC project

> I think you misunderstand the role of 2.6. See the seven steps under > "The recommended development model for a project that needs to support > Python 2.6 and 3.0 simultaneously..." in > http://www.python.org/dev/peps/pep-3000/#compatibility-and-transition. > Step 1 reads "Port your proje

Re: Re: Porting Django to Python 3.0 as a GSoC project

> So this means, though, that folks running from SVN will still need to > run setup.py every time they update, right? Not that that's a > dealbreaker -- I think Django-on-Py3k'ers will be on the cutting edge > anyway -- just wanna check. Correct. distutils operates using time-stamps, so it wi

Re: Re: Porting Django to Python 3.0 as a GSoC project

> The specific issues I've run into so far: > > * Exception-catching syntax (i.e. ``except Whatever as e`` vs. > ``except Whatever, e``). 2to3 fixes these, and transparently transforms "the except clauses. > * Unicode literals (u'...'). Likewise, 2to3 removes the u"" prefix. So leave the co

Re: Porting Django to Python 3.0 as a GSoC project

> > You can (probably) support Python 2.x and Python 3.x out of a single > > source tree. > > From what I've read, this is true as long as the X after 2 is >= 6. > That's a problem with Django's stated intent to support Python 2.3 on > Django's release 1.0. > > Please correct me if I'm wrong

Re: Re: Porting Django to Python 3.0 as a GSoC project

> I hope you won't take it the wrong way when I say I have an extremely > difficult time believing that. No hurt feelings, no. However, I would find it useful if you could add specific reservations and doubts to that. What aspects of Django (that I perhaps haven't touch yet) do you consider unma

Re: Re: Porting Django to Python 3.0 as a GSoC project

> Except if Django has a Python 3.0 version, say, this fall, that means > how many years of supporting two parallel versions of Django and > merging features and fixes back and forth between them? Please see my recent report: 0 years, 0 months, 0 days, 0 seconds. You can (probably) support Pyth

Re: Porting Django to Python 3.0 as a GSoC project

> I'm still a bit worried about the fact that, aside from Django being a > moving target and Python 3.0 being a moving target, WSGI for Python > 3.0 is *also* a moving target; there still seems to be a fair bit that > hasn't been settled on how things ought to work. That is the reason why I t

Re: Porting Django to Python 3.0

> I wasn't at PyCon, and haven't done any 3.0 porting work myself, so I > could be behind the times, but my understanding of current porting > advice (based on PEP 3000) was that it's not going to be possible to > support 2.x and 3.x from a single codebase in many cases (even with > 2to3) if

Re: Porting Django to Python 3.0

> Some of the things you've identified as "Django should..." are a little > problematic since one of the current requirements (at least for 1.0) is > "Django should work out of the box with Python 2.3". Some of your > proposed changes don't even work with Python 2.5, so we need to add a > few

Porting Django to Python 3.0

At the PyCon sprint, I started porting Django to Python 3.0. In the process, I had to make a number of changes to Python, so this port currently requires the Python 3.0 subversion head (soon to be released as 3.0a4). This port is just a start; it runs the tutorial with the sqlite3 backend, includ

Re: Freelance Systems Administrator - FreeBSD / Django / Apache

I've noticed that you have posted requests for Django developers in the past. On at least two occasions, someone asked who "we" is, and I would like to echo that question. Some of your other posts were much more vague than this one, but you did specify that location doesn't necessarily matter as

Re: SQL Server support: In core for "1.0" or external-only?

Looking in the query generation code (for both trunk and queryset- refactor), there's special case code for RegEx clauses and Oracle, as Oracle uses a function call syntax instead of an operator syntax. It would be great to have this generalized for use with other engines. SQL Server has no built

SQL Server support: In core for "1.0" or external-only?

The SQL Server backend in trunk is basically broken (parameter replacement doesn't work right), as well as missing features (introspection being the big one.) There have been many proposed patches, though lots of them go back to 0.91, and make lots of changes outside of the backend as well. On m