Re: Proposal: move non-db tests out of TransactionTestCase

[zalew]

> +1 to you proposal. Please open a ticket. 
>

done https://code.djangoproject.com/ticket/20004 

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Proposal: move non-db tests out of TransactionTestCase

[zalew]

Hi

I'm currently working on a project where I don't use db.* and I met a 
problem during testing. As django.test.testcases.TestCase [1] inherits from 
TransactionTestCase, it complains about "ImproperlyConfigured: 
settings.DATABASES". A solution is to fall back to SimpleTestCase (which 
TransactionTestCase inherits from), but this class doesn't contain useful 
test helpers, which aren't in any way related to db handling: 

* assertRedirects 
* assert(Not)Contains 
* assertFormError 
* assertTemplate(Not)Used 
* _urlconf_setup(teardown). 

Is there a reason why these functions were bound to a transaction handling 
test class instead of SimpleTestCase?

My proposal is to move them out either to SimpleTestCase, or a separate 
class other tests (including TransactionTestCase) can inherit from. I have 
experimentally written a SimpleTestCase based class for my needs, but I 
haven't yet tested it against the Django suite.

What do you think? If you agree and/or have some ideas, I will submit an 
issue and work on a patch proposal.

[1] https://github.com/django/django/blob/master/django/test/testcases.py

Cheerz,
Jakub Zalewski

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: How can we Commit request.FILES using pysvn in Django?

[zalew]

This is a group for discussing development of the framework. Please post 
your support questions to django-users.

On Tuesday, February 26, 2013 7:57:24 AM UTC+1, abdul wrote:
>
> I have to commit files from request.FILES to svn repository usiong pysvn 
> but when i try like this
>
> import pysvn
> client = pysvn.Client("Repo_url")
> file = request.FILES.get('file', None)
> *client.add(file)*
> *
> *
> *TypeError: PyCXX: Error creating object of type N2Py7SeqBaseINS_4CharEEE 
> from 
> *
> *
> *
> *Please help me out.*
> *
> *
> *Regards,*
> *Abdul Wahid*
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Djangopeople.net status

[zalew]

yeah. I got a few contacts through it, so it looks like it's positioned 
well and working, and I don't know if bringing .net back makes any sense. 
Most profiles will be redundant, won't they? Unless .net provides something 
more. We'd probably need a better djangogigs-alike.

On Friday, May 11, 2012 1:40:45 AM UTC+2, dstufft wrote:
>
>  djangopeople.me ? 
>  
> On Thursday, May 10, 2012 at 7:39 PM, Russell Keith-Magee wrote:
>
> On Thu, May 10, 2012 at 8:55 PM, Bruno Renié  wrote:
>
> On Thu, May 10, 2012 at 8:04 AM, Russell Keith-Magee
>  wrote:
>
> On Thu, May 10, 2012 at 9:19 AM, Aaron C. de Bruyn  
> wrote:
>
> On Wed, May 9, 2012 at 1:37 PM, Alex Sosnovskiy  
> wrote:
>
> https://convore.com/djangopeoplenet-development/ - gives http404
>
>
> Djangopeople.net is dead?
>
> If to be honest I don't understand you, guys! What's the profit of 
> rewriting
> views to class-based if djangopeople.net is down for a year ?
>
>
> That's because the rewritten code has never been deployed.
>
> Look at the whois record for djangoproject.com verses
> djangopeople.net.  I don't think djangopeople.net is officially part
> of Django.
>
>
> I can confirm for you -- djangopeople.net has never been an "official"
> part of the Django project. It was always an effort run outside of the
> official  (although Simon, the original developer, is a Django core
> developer).
>
> That said, I'm still interested in making djangopeople.net an official
> resource of the Django project. It was a very useful resource in it's
> time, which I for one miss. If anyone is interested (including Bruno,
> if he's still interested) in managing the project for the long term,
> let me know.
>
>
> I am still interested, the issue right now is to get admin access to
> the djangopeople.net DNS records and an up-to-date dump of the data.
> Regarding that, Simon Willison is pretty hard to reach and the best
> way to contact him is via Andew Godwin who can talk to him IRL. But as
> you may know, they're both busy people so that's why we're in the
> current situation.
>
>
> I'll shake the tree again and see what I can do.
>
> Another option would be to start from scratch; if we're making the
> official, we could host you at people.djangoproject.com, start with a
> clean database, and use the blog/mailing list/etc to get the word out
> and repopulate the database. It's less than ideal, but it would get
> over the hurdle. After all, we're perfectionists with deadlines :-)
>
> There is also the issue of hosting, at the time Andrew was happy to
> host the rebirth of djangopeople.net on ep.io but since it's closing
> down we'd have to find another option.
>
>
> As Jacob noted, the DSF can help out here. If you can come up with an
> estimate of what you need, I can put it to the board and get you those
> resources.
>
> Yours,
> Russ Magee %-)
>
> -- 
> 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 unsubscribe from this group, send email to 
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/django-developers?hl=en.
>
>  
> 

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/PWB8hlBxoegJ.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Moving to ... Github vs Bitbucket

[zalew]

Just wanted to ask from curiosity if it were other factors besides broad 
popularity, as BB is a great alternative. Most dev probably use both 
services, at least passively, as lots of good code is here and there, and 
I'm not against GH in any way. Per-line comments are actually a very good 
point, I hope BB will implement it. 

I'm a user, not a dev, so I'll take what you give (as most of us), and 
contribute where it is hosted, be it GH or BB. Cheerz, keep up the good 
work.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/FSaEQD-NpBsJ.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: start using less (and bootstrap!)

[zalew]

> We're going
> to solve that with our move to Git/GitHub, which will make it much
> easier for people to fork and much easier for core developers to
> integrate contributions.


a bit offtopic: why not http://bitbucket.org? similar features, it's on 
python/django and already popular in django community.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/uWdwl_1-_qIJ.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.