The original idea was to enable "auto_id_policy: legacy" to avoid scattered IDs. Do you remember, ...
10 years, 10 months ago
(2013-06-13 12:24:14 UTC)
#3
The original idea was to enable "auto_id_policy: legacy" to avoid
scattered IDs. Do you remember, Anatoly? It was your wish to have
clean IDs :)
To use the new setting in app.yaml (and for some refactoring in
auth_util) we need an up-to-date SDK. However, I've had some issues
using allocate_ids() then (and "auto_id_policy: legacy" didn't work,
most likely for the same reason why allocate_ids() isn't much suitable
for us. See my question here:
https://plus.google.com/u/0/117443360271789744397/posts/UpY8uVKxAym).
On Thu, Jun 13, 2013 at 1:56 PM, <techtonik@gmail.com> wrote:
> LGTM FWIW. =)
>
> https://codereview.appspot.com/10253046/
In that case I am for detecting version of SDK and reporting if we need ...
10 years, 10 months ago
(2013-06-15 16:18:07 UTC)
#4
Message was sent while issue was closed.
In that case I am for detecting version of SDK and reporting if we need a newer
one, and still maintain explicit version requirements. For example, this way
somebody may notice that we are still using Django 1.3 and help with porting.
On Sat, Jun 15, 2013 at 6:18 PM, <techtonik@gmail.com> wrote: > In that case I ...
10 years, 10 months ago
(2013-06-17 03:40:53 UTC)
#5
On Sat, Jun 15, 2013 at 6:18 PM, <techtonik@gmail.com> wrote:
> In that case I am for detecting version of SDK and reporting if we need
> a newer one, and still maintain explicit version requirements. For
> example, this way somebody may notice that we are still using Django 1.3
> and help with porting.
I don't think that it's needed to maintain something like a
requirements file. ATM the only requirement that Rietveld has is
Django 1.3 and that's distributed along the SDK and listed (with
version) in the libraries section in app.yaml.
--
Andi
>
> https://codereview.appspot.com/10253046/
On 2013/06/17 03:40:53, Andi wrote: > I don't think that it's needed to maintain something ...
10 years, 10 months ago
(2013-06-17 05:56:15 UTC)
#6
Message was sent while issue was closed.
On 2013/06/17 03:40:53, Andi wrote:
> I don't think that it's needed to maintain something like a
> requirements file. ATM the only requirement that Rietveld has is
> Django 1.3 and that's distributed along the SDK and listed (with
> version) in the libraries section in app.yaml.
Right. SDK has it all. As for the auto id policy, I am not ready to
switch to it yet. =)
Issue 10253046: Cleanup README a bit.
(Closed)
Created 10 years, 10 months ago by Andi
Modified 10 years, 10 months ago
Reviewers: dhermes, techtonik
Base URL:
Comments: 0