>
>
> Assuming the feature is accepted, at least a ticket and documentation are
> needed to finish the patch. See the patch review checklist:
>
> https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/submitting-patches/#patch-review-checklist
>
Documentation:https://github.co
>
> Yes, the patch must contain a call to posixpath.join somewhere. This is
> tricky to get right, don’t reinvent the wheel!
>
Agree, posixpath is the best solution. Forgot this module :(
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contri
>
> Asking again... I am not sure if the Django Template Language should
> evolve new features like this. Is there any prior art in Jinja2? Absent any
> other +1's, I guess I would be more comfortable accepting the feature if so.
>
I can't say anything about Jinja2, but for existing old project
>
> Syntax for relative path was changed from ... to ./../
>
Anyone can tell me what to do next? Just wait?
--
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 receiv
>
> I see you created a pull request:
>> https://github.com/django/django/pull/6318
>>
>
Syntax for relative path was changed from ... to ./../
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscr
>
> There are backwards-compatibility concerns as a leading dot can no longer
> be used in a template name, though if developers are following the advice
> about template namespacing it wouldn't be a problem.
>
Mimicking for python import paths it's just my proposal. If this violate
some guide
>
>
> Either way, I fail to see how that feature would be really useful.
>
I was need a refactor for large hierarchy of django templates. Moving
branches inside hierarchy is simple, if inheritance uses relative paths.
--
You received this message because you are subscribed to the Google Groups
> Hmm... I suppose the closest alternative we have would be to store the
> base template name in a variable and pass it in from the view.
>
If code for support template inheritance lives in views, it's
not convenient.
Here is code, that implement this feature for Django 1.4/1.9:
https://gith
Hi, All.
For django.template.backends.django.DjangoTemplates (filesystem and
app_directories) it can be very useful. This can be implemented?
WBR, Vitaly.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)&q
Awesome job guys!
Vitaly Babiy
On Sat, Apr 28, 2012 at 9:07 AM, Camilo Nova wrote:
> Great Job. This will make easier for a lot of people to be involved on the
> project.
>
>
> On Friday, April 27, 2012 10:08:09 PM UTC-5, Adrian Holovaty wrote:
>>
>> On Fri, Apr 2
a datetime that is naive it will just assume that it is the correct
timezone.
Thanks,
Vitaly Babiy
On Tue, Aug 17, 2010 at 7:09 AM, David De La Harpe Golden <
david.delaharpe.gol...@ichec.ie> wrote:
> On 17/08/10 04:24, Russell Keith-Magee wrote:
>
> > Adding timezone sensitivi
Hey,
I been doing a lot with timezone aware dates and I noticed that the mysql
store will not allow you to store a datetime aware datetime. I was wondering
if there is a reason why not convert theses dates to whatever is in the
settings using astimezone. And then save that date.
Vitaly Babiy
Vitaly Babiy
On Tue, Feb 9, 2010 at 3:16 AM, James Bennett wrote:
> On Tue, Feb 9, 2010 at 2:09 AM, Harro wrote:
> > - Make email unique and username non-required on the model. That would
> > make implementing something that authenticated by email a lot
> > easier :)
&
Thanks, for the pointer. I think even if this gets people think about the
problem its a good start, I will raise this question again after 1.2
release.
Vitaly Babiy
On Mon, Feb 8, 2010 at 6:46 PM, Karen Tracey wrote:
> On Mon, Feb 8, 2010 at 6:39 PM, Vitaly Babiy wrote:
>
>> Hey
have been involved in a big part of django if
I am not following protocol please let me know, Thansk.
Vitaly Babiy
--
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...@googlegrou
+1 for me, this will make my life a lot easier to implement a auto test
runner.
Is need to right up a proposal for change the code_change method a little,
but this is for another email.
Vitaly Babiy
On Sat, Jan 16, 2010 at 1:48 PM, Antoni Aloy wrote:
> +1 for me
>
> El 16/01/2
That could also work, another problem is that many times when I am debugging
using tests I will use something like pbd. In this case we will always need
a way to fall back to the single thread mode.
On Jan 15, 2010 2:38 AM, "Russell Keith-Magee"
wrote:
On Fri, Jan 15, 2010 at 9:59
have to
run each one on its own.
Vitaly Babiy
On Thu, Jan 14, 2010 at 4:16 PM, ptone wrote:
> This is probably just a curiosity, but I was playing with ways to test
> the raw power of my new 8-core mac pro and was looking at how to apply
> this to testing.
>
> By using multiproc
, Alex Gaynor wrote:
> On Sun, Mar 22, 2009 at 9:51 PM, Vitaly Peressada wrote:
>
>
>
>
>
> > Malcolm, I might take a stab on this later. Do you know if queryset-
> > refactor branch was merged into trunk?
>
> > On Mar 20, 10:52 pm, Malcolm Tredinnick
> >
Malcolm, I might take a stab on this later. Do you know if queryset-
refactor branch was merged into trunk?
On Mar 20, 10:52 pm, Malcolm Tredinnick
wrote:
> On Fri, 2009-03-20 at 05:08 -0700, Vitaly Peressada wrote:
> > @Malcolm:
>
> > I agree with you that there are some hole
years old. Is there anything I could to help, please
let me know.
On Mar 19, 7:04 pm, Malcolm Tredinnick
wrote:
> On Thu, 2009-03-19 at 05:17 -0700, Vitaly wrote:
> > I wanted json serialize a tree of django model objects: Schedule ->
> > Player -&g
Thanks, Bob. Added comment to the ticket.
On Mar 19, 12:03 pm, Bob Thomas wrote:
> On Mar 19, 8:17 am, Vitaly wrote:
>
> > I wanted json serialize a tree of django model objects: Schedule ->
> > Player -> django.models.User.
> > django.core.serializers.serialize
, 9:55 pm, Malcolm Tredinnick
wrote:
> On Wed, 2009-03-18 at 17:59 -0700, Vitaly wrote:
> > I am using django version 1.0 and ran into shallow copy limitation of
> > QuerySet.values() where it returns ints for ForeignKey columns. Here
> > is my take on deep copy implementat
I am using django version 1.0 and ran into shallow copy limitation of
QuerySet.values() where it returns ints for ForeignKey columns. Here
is my take on deep copy implementation.
def deep_values(o, *args, **kargs):
""" Converts instance of django.db.models object into dictionary.
24 matches
Mail list logo
