labofsahil/github-event-dataset-2012 huggingface dataset:
You should keep the `:all`. The create action should be on the `UsersController` instead.

If you want to provide a API endpoint to create users, it should be in `Api::V1::UsersController` in this case
' is there for better error reporting:

``The document 'Person' does not have a primary key and can not be d in a ToMany context.``


On 3. apr. 2012, at 21:34, Mitar wrote:

>> +
>> +    def __init__(self, of, attribute, related_name=None, default=NOT_PROVIDED, null=False, blank=False, readonly=False, full=False, unique=False, help_text=None):
>> +        super(EmbeddedListField, self).__init__(to=of, 
>> +                                                 attribute=attribute,
>> +                                                 related_name=related_name,
>> +                                                 # default=default, 
>> +                                                 null=null, 
>> +                                                 # blank=blank, 
>> +                                                 # readonly=readonly, 
>> +                                                 full=full, 
>> +                                                 unique=unique, 
>> +                                                 help_text=help_text)
>> +    def dehydrate(self, bundle):
>> +        if not bundle.obj or not bundle.obj.pk:
>> +            if not self.null:
>> +                raise ApiFieldError("The document '%r' does not have a primary key and can not be d in a ToMany context." % bundle.obj)
> 
> If you use `%r` you probably do not need `'` around?
> 
> --- 
> Reply to this email directly or view it on GitHub:
> https://github.com/mitar/django-tastypie-mongoengine/pull/1/files#r641309
Can we get an example of usage.  Eg. UserSerializer with a `days_since_joined` field.
Here's a mistake:

    w * QT_y

fails when y is 2d. I imagine something like

    w[(slice(None), ) + (numpy.newaxis, ) * (len(y.shape) - 1)] * QT_y

could force the broadcasting to work properly. Is there a better way of doing this?
I removed all references anywhere to 'hardcore'. But, if that's scary, we can just do the form for now and file a ticket to finish up for the spring game.
I love this diff!
Ok. This is still unusual since it's returning True without ever checking an org role or anything about the actor. If that is in fact the desired behavior, this method probably needs a new name and additional info in the doc block.
PS this is a really nice solution for creating the forms dynamically, well done!
+1 for extracting this into a function.
This should be calling ``raw_search`` & the extra space should go away.
the attribute to use changes in iOS5.1, but this plugin is only ever used in ios5.1+ so its fine not to handle the legacy methods.
Expected sandbox?
@samnang that sounds about right to me. I was going to "just do it" when the merge conflicts were resolved, but @madebydna if you want to take care of that I would appreciate it :smile:
So, could you extract it from the "askbot" sectin?
try{}catch{} exceptions was introduced in PHP5, so if you want to use it, you can rewrite whole file to match PHP5.
Lets change this to the Snarf message provided by @ishneur
can we get an sync test and async test here?

we have had enough inconsistencies already
yeah that sounds good, i'm wondering if we should make it another extension like json or jpps called utils or something or just put it in the dependences folder and compile in as needed
this is not used so remove
I personally like object encapsulation because we can hide any information a client would need to know about the native world in the object.