cles/elb-django-allowed-hosts/
Personally I would quite like to see an equivalent of the @csrf_exempt
decorator perhaps @allowed_hosts_exempt that could be use to mark the
health check method.
Andrew
--
You received this message because you are subscribed to the Google Groups
"Django develo
on User, but it seems like the "correct" way to do it. Maybe
Django could create a branch a la newforms to give people time to
transition?
-- Andrew
On Aug 18, 3:59 pm, Jonas Obrist wrote:
> James Bennett wrote:
> > On Mon, Aug 17, 2009 at 11:35 AM, James Bennett
> > w
ch does all the initialization setup.
Thoughts, ideas?
Thanks,
Andrew
--
http://www.apgwoz.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send e
Sorry, I mistyped the email address; moving to django-users
On Sep 10, 7:04 am, Andrew Gwozdziewycz wrote:
> Hello,
>
> What's the recommended place to put code that should be run once upon
> application initialization? I'm currently doing something along the
> lines o
On Thu, Sep 10, 2009 at 9:35 AM, Ryan K wrote:
> I'm trying to give advice to people but I can't even figure it out
> myself (even though it works for me just fine -- so far?).
Last week, I ran into a problem using them because I wanted to set manually
the date in certain situations. auto_now se
"it depends." We're stuck with auto_now, and auto_now_add, and they
work perfectly fine in some situations. They just aren't the be-all, end-all
solution to automatically saving date columns, as you so bluntly pointed out.
> On Sep 10, 1:19 pm, Andrew Gwozdziewycz wrote:
On Thu, Sep 17, 2009 at 10:04 AM, Russell Keith-Magee
wrote:
> As for likely roadblocks: I've been led to believe that Adrian has
> objections to framework-level logging. I have no idea as to the nature
> of his objection, but ticket #5415 indicates that he is (or has been,
> historically) in fa
On 9/24/09 9:56 PM, Ian Lewis wrote:
> On Fri, Sep 25, 2009 at 6:33 AM, Chris Beaven wrote:
>
>> +1 on the concept of a signing module.
>>
>> On Sep 25, 7:48 am, Marty Alchin wrote:
>>
>>
>>> The one downside to using get() directly, as opposed to an altogether
>>> new method, is that
Error originated. Yes, it's a little weird;
Python 3.0 handles this whole situation much better with "raise ...
from ..." which is intended for use in precisely these situations.
Andrew
--
You received this message because you are subscribed to the Google Groups
"Django d
rap_and_raise
another. I suppose you could examine the output of
`traceback.format_exc()` or one of its other functions to see if the
original exception is now mentioned in the traceback.
Andrew.
--
You received this message because you are subscribed to the Google Groups
"Django develope
a different
exception".
Andrew.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@
Why use regular expressions at all for this? A timeit benchmark shows
a greater than 4x speedup with a rangetest in a loop over the string:
def phone2number(str):
chars = {'a': '2', 'b': '2', 'c': '2', 'd': '3', 'e': '3',
'f': '3', 'g': '4', 'h': '4', 'i': '4', 'j': '5', 'k': '5', 'l'
}
> _phone_chars_compiled = None
>
> def phone2number(szinput):
> global _phone_chars_compiled
> if _phone_chars_compiled is None:
> _phone_chars_compiled = {}
> for i in range(256):
> a = chr(i)
>
What's the policy about all those references to release notes in the
docs? For example, the autoescape template tag [1] has "New in Django
1.0: Please, see the release notes", with a link to the 1.0 release
notes. When can these be removed?
It's clearly a bad idea to rely on the release notes as
write and submit a patch to change the function to use this behaviour -
we used to do it in South, before I started using the ``creation``
methods - but it's catering to such a small audience I'm not sure it's
worth it, and documenting this behaviour might be a better solution.
Andrew
ough for 1.2, but it's
something we should do and probably could go immediately on the 1.3
milestone.
I agree as well; I'll be happy to write the patch when we get around to
1.3 coding time.
Andrew
--
You received this message because you are subscribed to the Google Groups "
I read your initial proposal here as "code things in a sensible way",
not "actively monitor performance and correct on the fly". Using
pagination and making sure there's no memory leaks in the code's loops
is a great idea, attempting to self-optimis
Isn't the overhead of a function call negligible compared to executing
a database query or opening/closing a connection?
On Mar 27, 10:08 am, Russell Keith-Magee
wrote:
> Hi all,
>
> One of the new features in 1.2 are signals on m2m operations [1].
>
> Recently, Ticket #13087 was opened questioni
have them there
*post* action, as you can then safely modify the relationship again/do
some raw database queries on the data/use the relationship to do
traversal or iteration over the contents (although one might argue
that's also a case for having a pre-remove).
Andrew
--
You received
the hit of an empty signal is that significant
(there's a function call, an assignment, and an if statement); as a
percentage of runtime, it seems very small (someone feel free to prove
me wrong, though!)
Andrew
--
You received this message because you are subscribed to the Google Group
Umpires? Strike three off a curveball?
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@goo
my proposal for that is to
allow some mechanism to select the migrations directory per database
alias (be that in a router or a setting), and then have a --database
option on migrate - there's already going to be a way to provide
directories that aren't appname/migrations/, so thi
On 28/05/10 13:06, Andrew Godwin wrote:
Hi all,
As perhaps was inevitable, I'm proposing implementing part of a schema
migration backend in Django. I'm not sure if this is a 1.3 thing (it
may well be 1.4, perhaps with some implemented in time for 1.3 but not
exposed), but it'
7;s definitely not easy to choose.
Still, I think option 1 is just going to hold Django back - there's a
few things they fixed in 8.0, most notably (for me) the implementation
of information_schema, which any PostgreSQL schema-altering backend is
going to want.
Andrew
--
You rece
ppy to write a patch for the docs to change it to match should
people agree - I just feel like I'm missing something here, as it's not
been done yet.
Andrew
--
You received this message because you are subscribed to the Google Groups "Django
developers" group.
To post to this
separate installations of the
same app because they _have_ to have the same package name involves more
python path mucking around than just installing them on the global path
with different names.
Andrew
--
You received this message because you are subscribed to the Google Groups "Django
best move, unless we try to teach new users about
virtualenv, pip, dependency files, and the whole stack that a lot of
more advanced Django developers use. We certainly need to think about
teaching that stuff - it came up as a topic during djangocon.eu, but I
don't think any consensus was reached - but
e risk of guiding people down too narrow a path. I'm
really not very good at deciding the order and layout of documentation,
just at generating it in large amounts (see the mass of mostly
unnavigable words that is the South docs).
Andrew
--
You received this message because you are s
k. I'm
unfortunately not that much of a heavy virtualenv user, so I might just
take a stab at the first part, but I feel like there really does need to
be a bit more tutorial after all these years. I find it even funnier
that the section I'm proposing to add isn't one of thos
round to my first attempt at part 5, I'll include an
interjection somewhere in the other parts in the patch, and people can
see if they feel like it's not too much of a distraction.
Andrew
--
You received this message because you are subscribed to the Google Groups "Django
develo
s_polling app in
the great_britain_polling app.
Thanks for working on this problem.
Peace,
Andrew
On Tue, Jul 13, 2010 at 12:08 PM, Nate wrote:
> Hello. My name is Nate. Myself and my friend Marco would like to
> upgrade django permissions. We would like to brainstorm here first to
cause these changes involve removing or rewriting significant
portions of django.forms, and thoroughly break compatibility with the
existing manipulators, I'll be releasing it as a separate module rather
than a patch to django.
Andrew
--~--~-~--~~~---~--~~
You r
the opinion that the former is better, as it requires the
developer to explicitly take actions that may result in a loss of
information; and for those cases where the developer either needs
floats or doesn't care as much about the accuracy, he can use
models.FloatField, which
Looking at models.Manager, I noticed that for convenience it implements
many of the public methods of QuerySet, delegating the calls to its
query set. This obviously allows for more convenient behaviour, such
as writing MyModel.objects.filter(whatever) instead of
MyModel.objects.all().filter(wh
s the latter is an exception
that doesn't set a precedent :)
Cheers,
Andrew.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to djan
se this whole package as a candidate for
inclusion in Django as a replacement for manipulators; however, due to
other demands, I never got around to tidying it up or writing it up to
my satisfaction for this.
Andrew
--~--~-~--~~~---~--~~
You received this message be
#x27;s suddenly become a
problem for me :-b
I'm +1 on having widgets template-based also.
Andrew
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send
This is IMO the best argument for this change. Being able to have a
custom (but consistent site-wide) display of form labels & errors with
only template overrides would be very nice indeed.
Andrew
--~--~-~--~~~---~--~~
You received this message because yo
e reasons why one would want to use signed cookies?
What (presumably security) issues are they intended to overcome?
Andrew
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post t
opose
this change for inclusion in 1.0. I will undertake the work required
to produce the patch + docs + tests, but I'd like a decision from the
core devs as to whether they would like to see this in 1.0 or not.
Cheers,
Andrew.
--~--~-~--~~~---~--~~
You receiv
he decimal
module is already made available separately for use with Python 2.3
(see http://www.taniquetil.com.ar/facundo/bdvfiles/get_decimal.html).
To the best of my knowledge, Adrian has not yet commented on this
possibility -- which is actually why I posted this threa
was unable to get Postgresql running on
my machines.
So if anyone has MSSQL, Oracle, or Postgresql running and can try out
this patch and run the tests[2], please do! and post the results
here. There might be some additional typecasting needed, particularly
for Python 2.3 compatibility.
Cheers
I'm trying to run all the django tests under Python 2.3.5 (on OS X
10.4.8), and there are lots of failures (see below).
My settings file for the test is just:
DEBUG = True
DATABASE_ENGINE = 'mysql' # 'postgresql', 'mysql', 'sqlite3'
or 'ado_mssql'.
DATABASE_NAME = 'test'
On Jan 29, 4:50 pm, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> On 1/29/07 10:15 AM, Robert Myers wrote:
>
> > I'm seeing the same amount of errors on python 2.3.4, it appears the @
> > decorator syntax is being used in the modeltests/test-client/views.py.
And I was so used to decorators that
cept ImportError:
# Import copy of _thread_local.py from Python 2.4
from django.utils._threading_local import local
Andrew
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To pos
;s
highly inconvenient (I'm using a "vendor branch" strategy as described
in the subversion book); so I'm looking for a different way to manage
this sort of thing.
What tools do you use to manage your patched version?
Andrew
--~--~-~--~~~---~--~---
Thanks Michael, Ramiro, and David. I'll read up on the things you've
suggested.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@goog
on these suggested ideas, including any
additional changes you think might be appropriate that I have not covered here.
Andrew
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe f
py - but I think, given the
most recent TB election was uncontested and several long-time Django
contributors have told me they'd be more willing to join a TB that was less
strictly technical-all-the-time, that it makes sense for us to also look at
those requirements.
Andrew
On Mon,
my evolving belief in the need for
visible, servant leaders in OSS communities rather than trying to embrace a
flat hierarchy with mechanical checks and balances - but that is for another
day.
Andrew
On Mon, Oct 24, 2022, at 4:26 PM, James Bennett wrote:
> On Mon, Oct 24, 2022 at
r 3 people in the near future".
Again, I'm not saying "we should write a new DEP and *that'll* fix it", I'm
trying to come from a position of working out what we can and should be
*doing*, and then ensuring our rules match that.
Andrew
--
You received this message
g who
otherwise should.
Is there anywhere that we have a more clear outline of what we expect from
members both before they join and after? If not, could we have that
discussion here to clarify for future members?
Thanks,
Andrew
--
You received this message because you are subscribed to the G
sort of change. I'm more than willing to hear alternative
suggestions for what that change should be (though as outlined previously, I
really don't think that change should be "remove the entire current Board for
underperformance and have another election").
Andrew
On Wed, Oc
DEP shortly so it's more clear exactly
what I want to change at a written-rules level - I suspect feedback on a more
concrete proposal will help us talk about it more clearly.
Andrew
On Wed, Oct 26, 2022, at 4:55 PM, James Bennett wrote:
> On Wed, Oct 26, 2022 at 12:02 PM Andrew Godwi
d) as well as initial feedback on its content as
well.
I have copied in the DSF Members mailing list as it is a governance-related
DEP, but if we could keep all discussion on the thread in the Django Developers
mailing list, as per DEP 0001, that would be great.
Thanks,
Andrew
--
You received
o need to
really think about and have answers to if we take this forward.
(I didn't even discuss how we might fund this, which is also a conversation to
have, but waving our hands in the air and going "sponsorship" is enough for me
to start with)
Andrew
On Wed, Oct 26, 2022, at 4:0
lks feel welcome and
hopefully get more folks (who do fit the criteria) to apply.
If someone wants to draft new language, that would be great. If not, I may
have some time next week to try.
Thanks,
Andrew
P.S. Great meeting both of you at Djangocon last week!
On Thursday, October 27, 2022 at 7:4
On Sun, Oct 30, 2022, at 10:42 PM, James Bennett wrote:
> On Wed, Oct 26, 2022 at 4:34 PM Andrew Godwin wrote:
>> __
>>
>> I have copied in the DSF Members mailing list as it is a governance-related
>> DEP, but if we could keep all discussion on the thread in the Dj
able to me,
though if we are going to introduce this we should _also_ introduce wording for
what happens if we fail to elect a Board, as this makes it much more likely
(barring the entire previous board from running).
Andrew
--
You received this message because you are subscribed to the Google G
/end new language.
Borrowed the list of categories from Andrew Godwin's DEP for the update to
the technical board. Per Tim's recommendation, do we want to include
anything about the review process?
Also, I'm a little unsure about that last bit about applying, but I wanted
to put
Will do, Carlton.
Tim and Cory, thanks for the suggestions. I'll incorporate those in the PR
and post here when it's ready. Probably not today, but I should be able to
open it before the end of the week.
Thanks,
Andrew
On Tuesday, November 8, 2022 at 10:10:51 AM UTC-5 carlton...
Just want to pop in and say these are great ideas - feel free to copy me in
on any PR if you want extra opinions!
On Tuesday, November 8, 2022 at 8:26:28 AM UTC-7 Carlton Gibson wrote:
> Great, Thanks Andrew. No urgency 😊
>
> On Tue, 8 Nov 2022 at 16:16, Andrew Mshar wrote:
>
I like that idea, Tim. A few things came up, so I'll open this PR next week.
Thanks,
Andrew
On Friday, November 11, 2022 at 12:21:43 PM UTC-5 schill...@gmail.com wrote:
> Hi folks!
>
> Andrew (Mshar) how do you feel about reworking:
>
> > If you know someone who you thi
e DEP here:
https://github.com/django/deps/blob/main/draft/0012-steering-council.rst
My vote is +1, as I am the author of the DEP and believe it is in the best
interests of the longevity of the Django project and sustainable governance.
Andrew
--
You received this message because you are subscri
e DSF Board has performed
their vote, as it only seems appropriate.
Andrew
On Mon, Nov 28, 2022, at 9:30 PM, 'Adam Johnson' via Django developers
(Contributions to Django itself) wrote:
> +1 from me
>
> And +1 to using the forum in future
>
> On Tue, 29 Nov 2022 at 00:23
concluded and a result reached.
Andrew
On Wed, Nov 30, 2022, at 10:44 AM, Andrew Godwin wrote:
> Yes, I agree we can use the forum in future since it's less tied to Google.
>
> Provided the current +5 vote carries through to the end of the voting period,
> I will be suggesting that th
erate - the ability to
moderate after a post has gone out, rather than gating all posts behind
approval if they're untrusted, is a big step in itself, not to mention the
ability to remove sensitive or offensive content once it's posted.
Andrew
On Monday, November 28, 2022 at 10:0
s", as it'll be timed right after the
4.2 feature freeze in January.
Andrew
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving email
We should at least update those Trac and Triage Workflow docs to point to both,
maybe with the Forum first?
Andrew
On Thu, Jan 19, 2023, at 12:30 AM, Carlton Gibson wrote:
> I'm trying to begin new conversations there where I can.
>
> The main issue is that we're still p
ovember 11, 2022 at 1:52:07 PM UTC-5 Andrew Mshar wrote:
> I like that idea, Tim. A few things came up, so I'll open this PR next
> week.
>
> Thanks,
> Andrew
>
> On Friday, November 11, 2022 at 12:21:43 PM UTC-5 schill...@gmail.com
> wrote:
>
>> Hi f
This can be a fully qualified URL (e.g. "http://www.yahoo.com/
search/") or an absolute URL with no domain (e.g. "/search/"). Note
that this returns an HTTP status code 302.
---
Andrew Gwozdziewycz
[EMAIL PROTECTED]
http:
case would be. SingleObjectMixin is
designed to only ever give you one object back (though I'm surprised it doesn't
handle the MultipleObjectsReturned exception), so out of all the lookup choices
we have, only an exact match on a unique field makes sense. Am I missing
something he
On 16 February 2012 15:42, Łukasz Rekucki wrote:
> 1) I can't argue about popularity, because I have no data, but most
> Django applications I use come from github, so it's also quite
> popular.
>
> 2) I don't think Django should care if the collaboration tool runs
> python/django or java/grails a
it in the head (wontfix) or
euthanize it (Someday/Maybe) before people spend more time on patches.
Andrew
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To u
On Feb 27, 12:14 pm, Anssi Kääriäinen wrote:
> I happened to just post a comment to ticket 4102. The way forward is
> throwing out automatic changed field tracking and just implementing
> what the ticket was originally about: .save(save_fields=['somef']),
> which would then update field somef. Tha
https://code.djangoproject.com/wiki/SummerOfCode2012, but you're not
limited to just the ideas on that page, so feel free to propose other ideas.
Looking forward to seeing your applications!
Andrew
--
You received this message because you are subscribed to the Google Groups "D
or MSSQL
backends - three is already a lot of work, and they're harder databases
to get a hold of for testing.
Andrew
--
You received this message because you are subscribed to the Google Groups "Django
developers" group.
To post to this group, send email to django-developers
it's not always possible
(delete_index, delete_unique), but something that tries where it can,
and puts comments/invalid SQL where it can't, would be nice.
Andrew
--
You received this message because you are subscribed to the Google Groups "Django
developers" group.
To po
e
https://code.djangoproject.com/wiki/BetterErrorMessages page in
particular and look at some of the ideas in there - as each particular
area is quite small in scope, we'd be looking for a decent number of
error fixes to form a GSOC proposal that would be considered enough
work. There'
there something which I am not getting correctly?
I'm not sure - I've never had that one myself. It might have only been
with a previous version of the sqlite library or Python binding - have a
look through the history on the wiki page to see when it was put in
there, and by whom.
n
working for now and mirror some of the methods. Just make sure that
whatever you choose, it fits into the schedule, and you can justify it.
Andrew
--
You received this message because you are subscribed to the Google Groups "Django
developers" group.
To post to this group, send email
progress now and again and answer the
occasional design decision/gnarly core Django question. The ability to
work independently, make good decisions and research/justify them well
is a big part of GSOC, and something we're looking for.
Andrew
--
You received this message because you are sub
ectly - there's much more detail in my previous
post about the GSOC process.
Thanks,
Andrew
--
You received this message because you are subscribed to the Google Groups "Django
developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubsc
Hi everyone,
Just a quick reminder that there's only one day left for GSOC
applications - the deadline that they must be filed on the GSOC website
by is April 6th, 19:00 UTC (roughly 30 hours from now).
Andrew
--
You received this message because you are subscribed to the Google G
uld be nice - what's your
specific experience with the 3 main databases you'll be handling
(postgres, mysql, sqlite)? What was a "high voltage database migration"?
Sorry for the late feedback, I've been far too busy.
Andrew
--
You received this message because you are subscri
ustom creation code, and alteration types that differ from
creation types (much like SERIAL in postgres, which you _will_ have to
address) and room would have to be made for these kinds of problems.
Andrew
--
You received this message because you are subscribed to the Google Groups &q
to delay the evaluation
until after the urlconf has been initialised.
I don't think there's a real benefit to having a third approach.
Regards,
Andrew Ingram
On 8 Apr 2012, at 22:12, Martin Tiršel wrote:
> Hello,
>
> I just started to use class based views and I came to
www.google-melange.com/gsoc/project/google/gsoc2012/crodjer/24002
They should both be making a post here in the next week introducing
themselves and their projects - please feed back to them with your
suggestions and ideas.
Thanks also to everyone who helped discuss the proposals this year.
Andr
adds this facility to BaseFormSet, I
think the formset factories will need to hook into it as well.
Regards,
Andrew Ingram
On 24 April 2012 14:55, Tom Evans wrote:
> Hi all
>
> I raised a ticket about this new feature, with patch:
>
> https://code.djangoproject.com/ticket/18166
>
It seems to me there'd be more mileage in making new class-based
versions of the auth views.
- Andy
On 24 May 2012 13:51, Florian Apolloner wrote:
> Hi,
>
> -1 from me here.
>
> A) why don't you have site_name_name etc (those are still fixed).
> B) templates need to be able to rely on a name, if
Hi Iván,
I'd temporarily given up on getting extra_views into Django because of
a blocking issue with pagination and formsets.
Assuming a goal is to be able to build a new admin using class-based
views, there is a prerequisite of being able to paginate, sort and
filter on the querysets used for m
o like to see it possible at model
definition time, either using a decorator (like above) or a Meta
option like 'replaces'. The risk, of course, is that it means any
third-party app could override any other model without you necessarily
being aware of it, not sure how this would be mitigat
e API
proposal will come later along with details about how I plan to approach
the rest of the problem, but this is one of the few direct changes to
Django's core and so needs dicussion first.
Andrew
--
You received this message because you are subscribed to the Google Groups
"Django
On 7 June 2012 18:17, Andrew Godwin wrote:
> This means either having to register custom fields (like admin classes,
> for example), or requiring fields to live in a fields.py or fields
> package (like models and models.py). This is to provide for a
> less-fragile way of referring
On 07/06/12 20:14, Alex Gaynor wrote:
>
>
> On Thu, Jun 7, 2012 at 12:17 PM, Andrew Godwin <mailto:and...@aeracode.org>> wrote:
>
>
> In particular, I propose:
>
> - Requiring that all fields expose a method which says how to
> reconstruct them.
guarantee all field classes will be unique (especially as
fields have been around for ages). It also needs metaclasses - you can't
do it in Field.__new__, you need to do it in the metaclasses' __new__,
and if there's one thing I want to avoid it's adding more metaclasses.
Andrew
is someone changing database server and database
backend in sync, and for that you DO want to ignore the SQL completely -
if I go from PostgreSQL to MySQL (heaven forbid) I don't want South
thinking it should still try and use an IP column type.
Andrew
--
You received this message because you
o:xmlfield' (or
> whatever the key was previously).
Yes, I'd say versioning is unnecessary, as you can just use a different
name - the new migrations stuff will also include a much easier way to
delete older migrations from the history and thus wipe out-of-date
references, while still
On 08/06/12 16:45, Jacob Kaplan-Moss wrote:
> Hi Andrew --
>
> Generally I'm +1, and I think I see the point pretty clearly. Just a
> couple of questions:
>
> On Thu, Jun 7, 2012 at 7:17 PM, Andrew Godwin wrote:
>> - Requiring that all fields expose a method whi
On 08/06/12 17:42, Carl Meyer wrote:
> Hi Andrew,
>
> On Thursday, June 7, 2012 11:17:51 AM UTC-6, Andrew Godwin wrote:
>
> - Requiring that all fields expose a method which says how to
> reconstruct them.
>
> Essentially, it returns the positional and key
1 - 100 of 630 matches
Mail list logo
