Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Small change to setup.py, "pip installable" directly from the repository now. #1

Merged
merged 1 commit into from
May 12, 2011

Conversation

vitormazzi
Copy link
Contributor

I'm starting to use this project, and have the habit of installing it directly from github using pip, what was not possible due to the cleanup which was made at the end of setup.py.

I'm looking forward to collaborate in this project, as it is promising to be very useful to me. Is there any points in particular where you feel some work is needed?

@tomchristie
Copy link
Member

I'm looking forward to collaborate in this project, as it is promising to
be very useful to me.
Is there any points in particular where you feel some work is needed?

Fab! The first thing to do would be to join the discussion group:

http://groups.google.com/group/django-rest-framework

Secondly, the other way around - I'd really like to get your perspective
as a user on what you think needs improving,
and also - what would you be most interested in working on? Mostly I'm just
hugely happy to be starting to get some contributors to the project, feels
like it's passed a big hurdle. Absolutely any time you're able to spend
contributing is appreciated, whether it's bug reports, general feedback and
being active on the mailing list, or if it's actual checkins.

Some things I can think of that need some work.

  1. Core stuff (I'm currently working on, prob not worth other devs. worrying
    about this just yet.)
  • supporting nested resources
  • better reuse of resources between different views (involves decoupling
    resources from views)
  • removing requirement for absolute_url on models
  • a shortcut to automatically build a complete API for all installed
    models
  • framework for permissions
  • better automatic support of ForeignKey and related models.
  1. Authentication and permissions (Good ones to pick from)
  • OAuth authentication
  • Digest authentication
  • Authentication based on a token with a key/secret rather than based on
    user with username/password.
  • Throttling (I think marko is picking up on this)
  1. Parsers and emitters (Also good ones to pick from)
  • A file upload parser (ie for doing PUT to a view, with file content as
    the payload)
  • xml parser
  • yaml emitter + parser
  1. Documentation

I can give guidance on any of these if something jumps out at you?
I'm going to try to co-ordinate a push forward on the mailing list so I'll
prob be posting a similar list there shortly...

Thanks so much for the offer of help! It's really really appreciated!

t.

On 2 May 2011 16:35, vitormazzi <
[email protected]>wrote:

I'm starting to use this project, and have the habit of installing it
directly from github using pip, what was not possible due to the cleanup
which was made at the end of setup.py.

I'm looking forward to collaborate in this project, as it is promising to
be very useful to me. Is there any points in particular where you feel some
work is needed?

Reply to this email directly or view it on GitHub:
#1

tomchristie added a commit that referenced this pull request May 12, 2011
Small change to setup.py, "pip installable" directly from the repository now.
@tomchristie tomchristie merged commit 4e0aeb0 into encode:master May 12, 2011
nschlemm pushed a commit to nschlemm/django-rest-framework that referenced this pull request May 19, 2013
…-options

Merged work in progress for Issue 192 expose fields for options
tomchristie pushed a commit that referenced this pull request Oct 3, 2013
tomchristie pushed a commit that referenced this pull request Dec 3, 2014
mmarvick added a commit to mmarvick/django-rest-framework that referenced this pull request Jan 26, 2015
…Dict type from 'serializer.data', and also has a third item in the second usage
xordoquy pushed a commit that referenced this pull request Mar 11, 2015
tomchristie pushed a commit that referenced this pull request May 5, 2015
jpadilla pushed a commit that referenced this pull request May 27, 2015
Add drf-tracking to third-party-resources.md
jpadilla pushed a commit that referenced this pull request Oct 28, 2015
jpadilla pushed a commit that referenced this pull request Mar 1, 2017
Fixed Permissions.get_required_object_permissions for #4927
carltongibson pushed a commit that referenced this pull request Sep 20, 2017
* Add tests for schema exclusions

* Move exclusion check to should_include_endpoint

* Update docs

* Switch to using `schema = None`

* Test PendingDeprecationWarnings

* Add note to release notes.

* s/deprecated/pending deprecation/

* Add PR link to release notes

* Correct typo in test class name

* Test 'exclude_from_schema' deprecation warning message (#1)

* Correct deprecation warning message
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants