Re: Introduction & Contribution Interest – Django

Hello Ahmed The forum is way more active these days. It's worth repeating your introduction there, perhaps under membership: https://forum.djangoproject.com/c/internals/mentorship/10 . Balaji, you can also try asking there for support. Good luck all. On Fri, 14 Feb 2025, at 01:02, Thamarai Se

Re: Introduction & Contribution Interest – Django

Hi Balaji, If you add token validation globally like using session or jwt token authentication in middleware , generally all requests comes under the token validation in other words all endpoints are protected. But we will get token after login successfully. So here you have to make the login en

Re: Introduction & Contribution Interest – Django

Please share the specific piece of code where this token is being created. On Thu, Feb 13, 2025, 8:31 PM BALAJI V wrote: > 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."} > {"er

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

Re: Introduction

Try checking out an older commit and running the tests there. It may be that this doesn't work in all situations on the current latest commit on the master branch. On Tue, 14 May 2019 at 14:25, Ruchit Vithani wrote: > Hey Adam! I'm running tests same way as in that documentation. In tests > dire

Re: Introduction

Hey Adam! I'm running tests same way as in that documentation. In tests directory, I used `python -m pip install -r requirements/py3.txt` and then ` ./runtests.py`. I tried this again, but output is same. -- You received this message because you are subscribed to the Google Groups "Django dev

Re: Introduction

Hi Ruchit You should not be trying to 'pip install' the tests module. There is no tests module in Django's tree, there is a test directory that contains many individual test modules: https://github.com/django/django/tree/master/tests . You can see there's an i18n module in there. >From your trace

Re: Introduction

I've already installed requirements for tests. Before this, there was a module `tests` which wasn't present, and I installed it using `pip3 install tests`. This is the second module, which is not found. Am I missing something? This is a link to traceback: https://dpaste.de/XYTB -- You receive

Re: Introduction

I'm taking about this requirements, which are described in the documentation. On Tuesday, May 14, 2019 at 6:09:34 PM UTC+5:30, Ruchit Vithani wrote: > > I've already installed requirements for tests. Before this, there was a > module `tests` which wasn't present, and

Re: Introduction

I'm working now on ticket #30463 , and I've figured out what the problem is. Here, when self._meta_ordering is called, it returns instances of OrderBy type and, when .join is called on that list, it throws an error saying: expected str instance but O

Re: Introduction

Thanks, Tobias, for a wonderful explanation. I sure will try to add documentation about 'Reproduced at:' in triaging workflow. But currently, I've claimed one easy picking ticket, so once I finish work on that, I'll come on to this documentation :) -- You received this message because you are

Re: Introduction

Thank you Tobias. Good explanation. An additional point I picked up from Tim is that if you have a Reproduced at... but the bug is fixed on master then you have a starting point to git bisect where the issue was fixed. On Sat, 11 May 2019 at 15:28, Tobias Kunze wrote: > Hi Ruchit, > > On 19-05-

Re: Introduction

Hi Ruchit, On 19-05-10 23:19:16, Ruchit Vithani wrote: >I have following queries regarding tickets on Trac. In many of the tickets, >some people comment `Regression in` and `Reproduced at`, and both of them >link to some commit on GitHub. I could not understand what these links >specify. The "

Re: Introduction

I have following queries regarding tickets on Trac. In many of the tickets, some people comment `Regression in` and `Reproduced at`, and both of them link to some commit on GitHub. I could not understand what these links specify. I read this

Re: Introduction

Thanks! Carlton. Will surely check out those links. On Wednesday, May 8, 2019 at 5:46:33 PM UTC+5:30, Carlton Gibson wrote: > > Hi Ruchit, > > Welcome aboard! 🙂 > > There's a whole section on finding a ticket in the talk I gave at > DjangoCon Europe recently. Check it out: > > https://www.yout

Re: Introduction

Hi Ruchit, Welcome aboard! 🙂 There's a whole section on finding a ticket in the talk I gave at DjangoCon Europe recently. Check it out: https://www.youtube.com/watch?v=F4StlMFb5Ms In the Trac you can filter by component which helps: https://code.djangoproject.com/query?status=assigned&stat

Re: Introduction as a new member to django contributions mailing list

On the project home page https://www.djangoproject.com/ it has the link on how to contribute. https://docs.djangoproject.com/en/dev/internals/contributing If you have a specific question feel free to ask, but this is a good starting point. Dylan On Sat, Jan 26, 2019 at 10:51 AM Yemdjih Kaze Na

Re: Introduction GSoC

Also, if Django does participate in GSoC this year, they'll have an ideas page for it eventually similar to something like this - https://code.djangoproject.com/wiki/SummerOfCode2018. The best thing that you can do today to improve your chances is start contributing! -- You received this mess

Re: Introduction GSoC

am sorry Noumbissi you're a very welcome fellow . On Jan 21 2019, at 9:42 am, Noumbissi Valere wrote: > Thanks Carlton. > > On Mon, Jan 21, 2019 at 9:38 AM Carlton Gibson (mailto:carlton.gib...@gmail.com)> wrote: > > Hi Folks. > > > > First off: can we please keep it civil. Let's offer positive

Re: Introduction GSoC

Thanks Carlton. On Mon, Jan 21, 2019 at 9:38 AM Carlton Gibson wrote: > Hi Folks. > > First off: can we please keep it civil. Let's offer positive responses > where possible. Thanks > > There's no harm in people asking for help: there is a contributing guide, > but if folks aren't finding it, pe

Re: Introduction GSoC

Hi Folks. First off: can we please keep it civil. Let's offer positive responses where possible. Thanks There's no harm in people asking for help: there is a contributing guide, but if folks aren't finding it, perhaps we need a bigger sign-post. So... The place to begin is here: https://

Re: Introduction GSoC

Hello Noumbissi , I think you're skilled in python but you're not enough skilled in "" GOOGLEing" . you can start with the officiel django tutorial. https://docs.djangoproject.com/en/2.1/intro/tutorial01/ Best regards. On Jan 21 2019, at 1:50 am, noumbissival...@gmail.com wrote: > Hello Everyone

Re: Introduction : Somesh Chaturvedi

Sounds good. I'll join the group right away and look at all other possible ways of contribution you have mentioned. Thanks, Adam. On Thursday, December 21, 2017 at 6:13:07 PM UTC+5:30, Somesh Chaturvedi wrote: > > Hi everyone, > > I have been using Django in my professional as well as personal p

Re: Introduction : Somesh Chaturvedi

Welcome Somesh, There's actually a mailing list dedicated to first time contributors, where you might get a bit more attention: https://groups.google.com/forum/#!forum/ django-core-mentorship I'd suggest having a particular goal in mind where you'd like to contribute - what areas of Django do you

Re: Introduction for GSoC 2017

Welcome! It's a bit late to be starting on a successful proposal, especially if you haven't contributed to Django before, but good luck. I'm not sure if you were looking for anything specific in reply to your intro? On Monday, March 13, 2017 at 9:52:34 AM UTC-4, Gunpreet Ahuja wrote: > > Greetin

Re: Introduction GSoC 2017

Hi, Have you read the wiki page? https://code.djangoproject.com/wiki/SummerOfCode2017 It contains getting started tips. If so, please be more specific with your questions. On Monday, March 6, 2017 at 7:25:31 AM UTC-5, sahil jain wrote: > > Hello Everyone > I am a sophomore major in computer scie

Re: Introduction

Hi Naman, All the details for Django's GSoC program can be found on our wiki page: https://code.djangoproject.com/wiki/SummerOfCode2014 That page has a bunch of suggestions for projects, and details of what we expect of applicants. If you've got any more questions, let us know! Yours, Russ Mag

Re: Introduction

On Saturday, October 12, 2013 7:53:38 PM UTC+5:30, Daniele Procida wrote: > In particular you might want to choose something straightforward to begin > with, so look for tickets marked as "easy pickings": < > https://code.djangoproject.com/query?

Re: Introduction

On Sat, Oct 12, 2013, Jasvir Singh wrote: >I am Jasvir Singh, a student of Computer Science. >5-6 months ago, I started working on django and found it is a really >efficient tool. >Now I want to do some development for django. > >Can anyone please suggest me some task/project to do. Hi Jasvir. I

Re: Introduction to CRM

thanks man, I was looking for more information about how CRM works. On May 21, 4:04 am, Ankur <[EMAIL PROTECTED]> wrote: > Hi All, > > I just found a link which seems to be quite informative about CRM. > > Just try the link below to have a look at it. > > http://www.quazen.com/Business/Management

Re: introduction

Andy Shaw wrote: > PS: would Luke's GenericForeignKey allow for inline editing, assuming it > was to be adopted? Personally I'd much rather be able to alter a row's > permissions on its own admin page than have to switch table. There would have to be very specialised support for it. I haven't

Re: introduction

Thanks everyone for the ideas, I've updated the wiki page. Please take a look if you have a moment and let me know. Thanks, Chris --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post

Re: introduction

Hi Chris, The implementation detailed on the wiki appears to give the granularity that several people around here (including myself) have been looking for, minus the various points that have already been brought up. An ACL-type solution as opposed to UNIX-style permissions certainly seems more fl

Re: introduction

one more nit to add to my growing pile, while I use integer's as my keys (which is they default django way), others override this and use strings and other weird things. I'm not sure how my previous suggestion would work when you take that kind of thing into account. On 28/05/2006, at 9:04 A

Re: introduction

> How do you deal with those permissions in the generic and admin views? To be clearer, I meant: How do you deal with those permissions in the generic and admin *list* views? -rob --~--~-~--~~~---~--~~ You received this message because you are subscribed to the

Re: introduction

Hi Chris, I have a little feedback if you are interested. [Just so you know, I'm a "heavy user" of Django but have yet to make a substancial contribution to the project] In general I think your proposal is fine but I have a few points: -Lots of tables there! Can you acheive the same without the e

Re: introduction

I think that multiple tables are better because its easier to manage - you can use foreign keys inside the DB, thus it can be faster and clearer plus its easier to drop a table than delete many rows. I gave this feature a lot of thought (I thought of applying for it myself ;) ), here are some of m

Re: introduction

Hi Chris... great write up. my only thought was: why do you need multiple tables to store the row level permissions? Luke has recently submitted a 'GenericForeignKey' in http://files.lukeplant.fastmail.fm/public/python/lp_tagging_app_0.1.zip which may be of interest. it would allow you to sto

Re: introduction

Hi Ian, Wrote up a summary on the wiki page: http://code.djangoproject.com/wiki/RowLevelPermissions Please let me know what you think, if anyone else has any input please let me know. Right now, I'm working through the source code in more depth then my previous exploration of it, and will be mo

Re: introduction

Hi Chris. why not post your idea onto the list. it's much easier to critique something than wave hands around. you might also want to set up a wiki page on say http:// code.djangoproject.com/wiki/RowLevelPermissions or something I've my own thoughts, but I'd rather see what you have than dicta

Re: introduction

Guess I'll just continue this thread. My name is Chris, another one of the SoC students. I'm working on per row permissions, so if anyone has any ideas on it, please let me know. I have my own idea, but what I think works might be horribly wrong for everyone else. Not to say that my idea sucks. ;