I bumped into this old WONTFIX. And I agree with the decision not fix it in
the way proposed by OP. But the current behaviour can be very confusing:
https://code.djangoproject.com/ticket/32023#comment:3
That `del ` I propose would be free if nothing has accessed `headers` yet
or nothing will b
RM to do this for you. If frequently need to do this for *the
same* query, you can't really do it in a custom queryset without overriding
_fetch_all, assembling the dictionary there and gluing collections onto
instances there, which doesn't feel like a good thing to do.
So I would suggest
ld
still be configured to be deterministic by passing --no-random / --sorted
or whatever the opt-out option would be called. But, regardless of the
default, to get the full benefit I think you'd want at least one of the
test runs in CI to be a random one.
--Chris
>
--
You recei
://docs.python.org/3/library/random.html#random.Random
and the random orders could be generated by calling methods of that
now-deterministic object.
--Chris
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
Hi Warren
This is excellent news!
Thanks
Chris
On Fri, 27 Nov 2020 at 01:40, Warren Chu wrote:
> Hi All,
>
> Microsoft has now committed ongoing resources towards improving MSSQL and
> Azure SQL support for Django. We're currently focused on internal
> compliance and for
Hey all,
Just wondering what the future of this is looking like?
CB
On Friday, 12 April 2019 07:33:35 UTC+1, Shaggy wrote:
>
> and how it is going ?
> is there some interest from django devs?
>
> On Monday, 4 June 2018 15:18:23 UTC+2, Andrew Godwin wrote:
>>
>> Hello everyone,
>>
>> For a while
Thanks Adam will do!
On Thursday, 18 April 2019 16:36:48 UTC+1, Adam Johnson wrote:
>
> Hi Chris!
>
> I'm not a Windows user, but I guess something in your Windows
> configuration is making the Python file open in VSCode rather than get run
> by the Python interpret
tput. It may
be running in the background.
When I use
...\> python runtests.py
It works.
Do I need to configure something in windows for it to work without the python
prefix?
Or should the python prefix be added to the docs?
Thanks
Chris
--
You received this message because you are su
My guess is this does not work on MySQL or SQLite, since as far as I can tell
it’s the only DB that will return IDs when bulk inserting. I’d think you’d have
to have some other code path to handle those DB backends.
--
You received this message because you are subscribed to the Google Groups
The problem is the version of SQLite included in recent versions of macOS. The
easiest fix we saw was installing Homebrew and then doing a `brew install
sqlite`.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)"
attack vector.
Thanks for the feedback,
Chris
On Thursday, September 22, 2016 at 2:41:22 PM UTC-4, Aymeric Augustin wrote:
>
> On 22 Sep 2016, at 20:32, James Bennett >
> wrote:
>
> > So personally I'd like to hear some more about why this is seen as
> ne
Huzzah! Looking forward to the new syntax landing.
On Sunday, May 21, 2017 at 2:56:13 AM UTC-5, Aymeric Augustin wrote:
>
> Hello,
>
> The technical board accepted DEP 201:
> https://github.com/django/deps/blob/master/accepted/0201-simplified-routing-syntax.rst
>
> Sjoerd has taken the lead on t
On Tuesday, April 18, 2017 at 1:25:36 PM UTC-5, Tim Allen wrote:
>
> Thanks for the kind words. To answer your questions:
>
> - It is also my hope to automagically create version friendly links, so we
> don't see a commit on each Django release.
>
This ought to be useful to sub in where necessa
Look through https://code.djangoproject.com/wiki/SplitSettings for many
different approaches to loading settings from files that aren't importable
as Python modules.
My personal favorite is django-split-settings, which would let you
accomplish exactly what you're trying to do.
On Thu, Apr 6, 201
Thanks Aymeric! I'll give that a try next time!
On Wednesday, March 8, 2017 at 3:20:31 PM UTC-6, Aymeric Augustin wrote:
>
> Hello,
>
> On 8 Mar 2017, at 21:23, Chris Foresman >
> wrote:
>
> I'll chime in to say I've had a similar problem related to the
I'll chime in to say I've had a similar problem related to the shell and I
couldn't sort out how to address it.
Our database servers will drop connections that last longer than 10
minutes. So basically can never do a task I might otherwise use the shell
for that would take longer than 10 minute
The way django's authentication system works is that when you register, you
send the password to the server, then the server runs that password through
some hashing algorithms, then the resulting hash is stored in the database.
When the user logs in, the password again is sent to the server, and
Out of curiosity, why isn't this added as part of the column definition?
Isn't it better to enforce the default at the DB layer? Or is it to account
for differences across database types? (This trips me up a lot because we
have a lot of different apps/processes which have to touch the database a
scale down as well
> as up.
>
> Andrew
>
> On Mon, Sep 26, 2016 at 1:30 PM, Chris Foresman > wrote:
>
>> Why would you be running a small website in ASGI mode with a single
>> worker? My suspicion is that someone using Django in ASGI mode has a
>> s
call a pathological case is a small website, running on
> something like cheap VPS.
>
>
>
> 2016-09-26 15:59 GMT+02:00 Chris Foresman >:
>
> > Robert,
> >
> > Thanks! This really does clear things up. The results were a little
> > surprising at
on a
single machine would be an interesting next step, no?
Anyway, thanks for taking the time to do this work and help us understand
the results.
On Sunday, September 25, 2016 at 8:23:45 PM UTC-5, Robert Roskam wrote:
>
> Hey Chris,
>
> Sure thing! I'm going to add a little col
e the change would be 3.7. If the time between 3.6 and 3.7 is the same
as the expected time between 3.5 and 3.6 (see [1] and [2] for those
schedules), then 3.7 would be released in March 2018. Django users using
Python 2.x or 3.6 or lower would never see the change if it's changed in
Python a
od to use the dotted name instead of unittest's
current, less helpful format. Django already has an example of subclassing
TextTestResult with its DebugSQLTextTestResult class.
Thanks,
--Chris
--
You received this message because you are subscribed to the Google Groups
"Django develope
I'd really, really like an alternate URL resolver which does typecasting. I
mean, if I'm specifying the type right there, why not expect the resolved
to be the type I just specified? In 995 of URLs, you're talking about three
basic types anyway: strings, integers, and (increasingly) UUIDs. After
Yes. Honestly, just explain what these results mean in words, because I
cannot turn these graphs into anything meaningful on my own.
On Monday, September 12, 2016 at 8:41:05 PM UTC-5, Robert Roskam wrote:
>
> Hey Chris,
>
> The goal of these tests is to see how channels performs
Is this one worker each? I also don't really understand the implication of
the results. There's no context to explain the numbers nor if one result is
better than another.
On Sunday, September 11, 2016 at 7:46:52 AM UTC-5, Robert Roskam wrote:
>
> Hello All,
>
> The following is an initial repor
I'm looking forward to contributing however I can to the project! Exciting
news!
On Friday, September 9, 2016 at 9:58:24 AM UTC-5, Andrew Godwin wrote:
>
> Hi everyone,
>
> The Technical Board approved Channels as an official Django project as per
> DEP 7, and so the repositories have been move
ary/ms188362.aspx
On Thursday, September 8, 2016 at 11:36:03 AM UTC-5, Tim Graham wrote:
>
> Maybe the fields from django-mysql help?
>
> http://django-mysql.readthedocs.io/en/latest/model_fields/resizable_text_binary_fields.html
>
> On Thursday, September 8, 2016 at 10:56:15 AM
I had a need to store an encrypted bytestring, and CharField doesn't work.
But BinaryField uses LONGBLOB by default (at least on MySQL). Doesn't it
make more sense to have a BinaryField equivalent of CharField, and use
LONGBLOB for something analogous to TextField? As far as I can tell, the
MyS
Nice work!
On Thursday, July 14, 2016 at 10:36:19 PM UTC-5, Andrew Godwin wrote:
>
> I am happy to report that the Official Projects DEP, number 0007, was
> approved by the Technical Board and is now adopted as final!
>
> Andrwe
> On 4 Jul 2016 11:39 am, "Andrew Godwin" >
> wrote:
>
>> I've revi
FWIW, we used to tell clients that Django offers a basic admin interface
"for free". However, we NEVER had a client that was sufficiently familiar
with what a database is or how data modeling works for this to ever
suffice. The first thing we always do on new project is immediately disable
the
tion but with Value:
> >
> > Whatever.object.filter(is_active=Value('false'))
> >
> > The ORM can't predict the type of a Value call - pretty much by
> definition,
> > since it's a raw value passed to the database. So you might be able to
> fi
Sorry, sbrandt noted the issue of subtle bugs, not Maxime.
On Friday, January 29, 2016 at 4:37:51 PM UTC-6, Chris Foresman wrote:
>
> I have to agree here; it's pretty sloppy to not enforce an explicit
> boolean value and can lead to subtle bugs. In addition to the one mentione
I have to agree here; it's pretty sloppy to not enforce an explicit boolean
value and can lead to subtle bugs. In addition to the one mentioned by
Maxime, consider the case of a nullable boolean field:
>>> bool(None)
False
Maybe that field has a better converter for possible values and explicit
+1 on setting. That's what I've ended up doing on all of my projects
anyhowways.
On Friday, January 29, 2016 at 2:45:02 PM UTC-6, Tim Graham wrote:
>
> In another thread about adding a "scheme" field to the Site model [1], I
> floated the idea of moving the data stored by the Site model into a
I used Jira at my previous company. It is a great tool, but it is
_extremely_ heavyweight. Unless you need to high level of customisation of
workflows and integrations it can provide, and have someone intimately
familiar with it and/or have the nearly-full-time job of learning and
fiddling with
For whatever it's worth, our company switched from Pivotal Tracker to JIRA
because we added a QA team and they wanted all this flexibility in devising
bug ticket "workflows." All it did from my perspective is add 47 layers of
complexity on top of a massively confusing UI and insists on NOT suppo
Also consider the media files could number into the millions (or
bajizillions?). Particularly for, say, a image hosting application. Clearly
it would not be feasible to enumerate all the files, and there would
clearly be regular additions. It might be that this use case is simply
"beyond the sc
Also consider the media files could number into the millions (or
bajizillions?). Particularly for, say, a image hosting application. Clearly
it would not be feasible to enumerate all the files, and there would
clearly be regular additions. It might be that this use case is simply
"beyond the sc
Donald could probably provide more information, but this post from April
shows the Python 3.2 numbers downloading from PyPI are constant, and pretty
small [https://caremad.io/2015/04/a-year-of-pypi-downloads/] His take was
that CI systems (like Django's!) were doing most of the Python 3.2 package
d
of the `startapp` template without .py extensions but, of
course, ensuring they end up as .py after rendering. (Or we use some
entirely different mechanism.)
My current implementation is
<https://github.com/django/django/pull/5735>; see some additional
comments I made there.
Regards,
-
We usually just handle this with a custom serializer (or form) field that
converts all input to lowercase. That way we don't have to change any
lookups or anything; all emails that come in to the system are already
lowercase. Of course, that doesn't preserve what users enter but IME
anything up
Jon,
You proposal seems like a sane and welcome change that aligns the exit
status of --exit with long-standing convention.
Thanks,
Chris
On Wednesday, October 21, 2015 at 10:20:09 AM UTC-5, Jon Dufresne wrote:
>
> On Tue, Oct 20, 2015 at 9:29 PM, Gavin Wahl > wrote:
> &g
For an additional non-core dev data point, I'm also +1 on Loic's 1.10,
1.11, 2.0... plan. Makes it much easier to plan and communicate framework
upgrades to clients.
On Tuesday, June 23, 2015 at 9:14:25 PM UTC-5, Josh Smeaton wrote:
>
> I was worried about 1.10 because I wrongly assumed that t
Hey Tim,
Sorry if this may be an unnecessary question but the ticket 24704
(Development server does not restart on syntax errors) seems to be a
regression and not a fix. I was previously on version 1.6.x and the
development server would continue to run if there were syntax errors. The
only cha
I'm really curious to know if the version to follow 1.9 is planned to be
2.0 or 1.10. I feel as though 1.x releases have had a lot of major feature
changes. Maybe it's time to start thinking about features in terms of
major, minor, and bugfix/security patch, and start saving major features
for
This is what we're using to send to loggly. I'm not honestly 100% sure it
works as intended but it gets the job done. It would be great if we could
conditionally log to console when running in a local dev environment.
LOGGING = {
'version': 1,
'disable_existing_loggers': True,
'form
Yeah, this is the point I was trying to make. I absolutely get your point
about the impact to user, though, Josh. It just seems worth doing since
this is an LTS release.
On Friday, February 27, 2015 at 5:41:12 PM UTC-6, Daniel Hawkins wrote:
>
> I'd bet an extremely large portion of those users
On Thursday, February 26, 2015 at 10:25:02 AM UTC-6, Thomas Leo wrote:
>
> I've opened a ticket [1] to implement the popups in the admin as modal
>> instead
>> of windows. I'm no UI/UX expert but modals are more or less the standard
>> today,
>> windows looks like a relic from the 2000s.
>
>
Given that 1.8 is an LTS, and increasing the default username length
addresses the 80% use-case for custom user models, isn't it worth adding
this change now (even if it philosophically violates the alpha/beta split)?
On Wednesday, February 25, 2015 at 12:24:20 PM UTC-6, Tim Graham wrote:
>
>
Diana,
I've been working on my own first patches to Django. I'm available all day
tomorrow from about 8-5:30 CST if you want any help with the basic steps.
You'll basically want to fork django/django, git clone that to your local
machine, and set the original repo as your upstream remote to get
Tim,
Our company is having our quarterly "hack days" next Thursday and Friday.
Can we sync up to work on some patches then?
On Thursday, February 12, 2015 at 8:07:46 PM UTC-6, Tim Graham wrote:
>
> If you would like to contribute to the timely release of 1.8 and if you
> have some free time o
Tim,
Why don't they build on 14.04? We regularly run Django on EC2 VMs with
14.04 as the base AMI.
On Monday, January 26, 2015 at 11:33:11 AM UTC-6, Tim Graham wrote:
>
> The pull request builders are now running on Ubuntu 14.04. The master
> still runs 12.04 and handles builds for versions o
ave time to chase
it down what's going on.
Running tests in PyCharm's debug mode takes over 10 minutes (!!) to create
the test DB, effectively eliminating our ability to use step-through
debugging of unit tests.
-Chris
On Fri, Dec 19, 2014 at 9:30 AM, Tim Graham wrote:
>
> Yes.
5 PM UTC-5, Shai Berger wrote:
>
> On Tuesday 21 October 2014 18:23:44 Chris Foresman wrote:
> > Is there some benefit to using `.callproc()` over this?
> >
> > ``` python
> > query = 'CALL sp_recommendation_engine(%s, %s)'
> > profile
Is there some benefit to using `.callproc()` over this?
``` python
query = 'CALL sp_recommendation_engine(%s, %s)'
profile = user.get_profile()
cursor = connection.cursor()
cursor.execute(query, [user.id, profile.id])
```
On Monday, October 20, 2014 1:29:49 PM UTC-5, Carl Meyer wr
On Tuesday, August 19, 2014 4:53:39 PM UTC-5, Chris Foresman wrote:
>
> On Tuesday, August 19, 2014 4:49:10 PM UTC-5, Chris Foresman wrote:
>
>>
>>
>> On Monday, August 18, 2014 12:05:55 PM UTC-5, Florian Apolloner wrote:
>>>
>>> Validation errors
On Tuesday, August 19, 2014 4:49:10 PM UTC-5, Chris Foresman wrote:
>
>
> On Monday, August 18, 2014 12:05:55 PM UTC-5, Florian Apolloner wrote:
>>
>> Validation errors are only caught inside form validation. Forms set the
>> password usually in save, not in clean,
On Monday, August 18, 2014 12:05:55 PM UTC-5, Florian Apolloner wrote:
>
> Validation errors are only caught inside form validation. Forms set the
> password usually in save, not in clean, so I don't think that patch covers
> it (or at least the relevant forms have to call validate_password in
+1 on GitHub OAuth. I've avoided filling or commenting on bugs because
setting up Yet Another Account was enough friction that I never did it.
On Thursday, August 7, 2014 2:21:06 AM UTC-5, Erik Romijn wrote:
>
>
> Using GitHub makes sense as it's very likely a new contributor already
> has a Gi
As a non-core community member, I welcome a streamlined way for new
potential coders to contribute.
On Thursday, July 24, 2014 7:02:16 AM UTC-5, Russell Keith-Magee wrote:
>
> Hi Aymeric.
>
> A big +1 from me. Thanks for all your work drafting these modifications.
>
> Russ %-)
>
> On Wed, Jul 23,
Looks good, Aymeric!
+1
On Thursday, July 24, 2014 1:30:13 AM UTC+12, Aymeric Augustin wrote:
>
> Hello,
>
> I’ve been working on updating our organization:
> https://github.com/django/django/pull/2947
>
> This proposal attempts to address several issues with our current
> organization. There
ect a Function that it doesn't
understand in the expression tree, give it a chance to render itself, and
if that fails then it could raise a warning or an error?
Cheers, Chris.
--
Aptivate | http://www.aptivate.org | Phone: +44 1223 967 838
Citylife House, Sturton Street, Cambridge, CB1 2Q
re that backend needs to render a particular
feature differently?
Cheers, Chris.
--
Aptivate | http://www.aptivate.org | Phone: +44 1223 967 838
Citylife House, Sturton Street, Cambridge, CB1 2QF, UK
Aptivate is a not-for-profit company registered in England and Wales
with company number
Hi Daniel,
The proposal looks interesting - I've only skimmed it so far but one
question: you mention User.get_model() several times -- do you mean
User.get_meta()?
On Saturday, May 24, 2014 7:05:02 AM UTC+12, Daniel Pyrathon wrote:
>
> Hi all,
>
> In the last days I have built a documentation
I like the idea, I've been using a custom script that does the first mode
of this tag nearly exactly the same way (with the same security escaping).
Not the biggest fan of the second mode of operation since like you say,
it's not compatible with strict CSP. Why not just encourage people to do it
On Saturday, May 3, 2014 6:10:39 AM UTC+12, Cal Leeming [Simplicity Media
Ltd] wrote:
>
> This approach seems to work fine, but doesn't appear to be mentioned
> anywhere in the Django docs (or at least, I couldn't see it).
>
> Would this be a valid candidate for a docs patch?
>
Hi Cal,
The 1.6
Hi Andrew,
On Sun, 6 Apr 2014, Chris Wilson wrote:
On Sun, 6 Apr 2014, Andrew Pashkin wrote:
* It makes it much harder to write custom assertions and get meaningful
display on error.
Can you give an examples for cases with messages/breakings and for custom
assertions?
I don't ha
umented (afaik) and (b) relies on
understanding of Python bytecode which is definitely not common knowledge.
Cheers, Chris.
--
Aptivate | http://www.aptivate.org | Phone: +44 1223 967 838
Citylife House, Sturton Street, Cambridge, CB1 2QF, UK
Aptivate is a not-for-profit company registered
tyle assertions. But better integration of Django and Pytest, and
the ability to write tests with Pytest-style assertions if you like, would
certainly have my support (fwiw).
Cheers, Chris.
--
Aptivate | http://www.aptivate.org | Phone: +44 1223 967 838
Citylife House, Sturton Street, Cambridge, C
t present, so in a sense it is required.
I know it's a very minor issue and I can easily work around it (however
ugly that is), but would it logically make sense for this field to be
required if pk is not None?
Cheers, Chris.
--
Aptivate | http://www.aptivate.org | Phone: +44 1223 9
Hi Carl,
On Tue, 18 Mar 2014, Carl Meyer wrote:
On 03/18/2014 02:54 PM, Chris Wilson wrote:
1. GCBV and Vanilla Views do a great job for simple forms, but they
leave out embedded formsets entirely. (For example our large form has
repeating sections for employment history, education, etc.) It
ject.com/ticket/15924, which was closed as "too
broad", and the required attribute part of it never made it into a
separate ticket, but it seems like it might be useful.
7. Uploaded files appear to be lost if form validation fails, since the
model isn't saved.
Thanks in adva
sion of the docs)
- a PDF export (for the PDF version of the docs)
OpenOffice Draw does export to SVG and PDF. We might also want a .PNG
fallback for browsers that don't support SVG (well).
Cheers, Chris.
--
Aptivate | http://www.aptivate.org | Phone: +44 1223 967 838
Citylife House, Sturto
.
* Profile and speed up the test suite, so that we can run all tests more
quickly, especially with databases like postgres where it takes an hour to
run them all.
Cheers, Chris.
--
Aptivate | http://www.aptivate.org | Phone: +44 1223 967 838
Citylife House, Sturton Street, Cambridge, CB1 2Q
tation patch if necessary, so someone would just
have to approve it.
Cheers, Chris.
--
Aptivate | http://www.aptivate.org | Phone: +44 1223 967 838
Citylife House, Sturton Street, Cambridge, CB1 2QF, UK
Aptivate is a not-for-profit company registered in England and Wales
with company number 04
Hi all,
On Fri, 14 Feb 2014, Florian Apolloner wrote:
as Tim noted on the ticket, we are not going to backport this as per our
policy.
In that case will you accept patches to remove description of the
broken feature from the documentation for 1.4, 1.5 and 1.6?
Cheers, Chris.
--
Aptivate
r>
but it actually doesn't in 1.6, please would you consider backporting this
fix to the 1.6 stable branch?
Cheers, Chris.
--
Aptivate | http://www.aptivate.org | Phone: +44 1223 967 838
Citylife House, Sturton Street, Cambridge, CB1 2QF, UK
Aptivate is a not-for-profit company registered in E
bt you're the first, or will be the last
person to think of this idea).
Thanks, I've created ticket https://code.djangoproject.com/ticket/21949,
with some more information on my reasons for proposing this.
Cheers, Chris.
--
Aptivate | http://www.aptivate.org | Phone: +44 1223 967 838
C
quest as stated
above. Is that likely to be accepted?
Cheers, Chris.
--
Aptivate | http://www.aptivate.org | Phone: +44 1223 967 838
Citylife House, Sturton Street, Cambridge, CB1 2QF, UK
Aptivate is a not-for-profit company registered in England and Wales
with company number 04980791.
--
Yo
On Tuesday, December 17, 2013 8:12:43 PM UTC-6, Russell Keith-Magee wrote:
>
>
> My claim is that complete abstraction of the data store shouldn't be the
> goal. What we should be aiming for is sufficient API compatibility to allow
> for two things:
>
> * ModelForms wrapping a model from a NoS
ime, this question will continue
to be asked until a position is officially documented, even if it's "we
don't care about NoSQL, just leave us alone."
Cheers, Chris.
--
Aptivate | http://www.aptivate.org | Phone: +44 1223 967 838
Citylife House, Sturton Street, Cambridge, CB
to run pure Python code
makes this rather easy and reduces the temptation to cram too much logic
into an ORM chain.
Chris
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails
I'm not asking anyone to do my job for me (I hope) but it would be really
nice to have something like 3 years of support for core infrastructure
like Django, that's really painful to upgrade, and even more painful to
replace. It would certainly help me to sleep better at night.
Chee
It looks like this issue has been marked as wontfix in
https://code.djangoproject.com/ticket/14952
However, I've used the following in manage.py to support running management
commands when distributing only .pyc files:
https://gist.github.com/cchurch/6067733
On Tue, Jul 23, 2013 at 6:29 PM, J
dels.Model):
published_date = models.DateTimeField()
objects = CustomManager(MyQuerySet)
Cheers, Chris.
--
Aptivate | http://www.aptivate.org | Phone: +44 1223 967 838
Citylife House, Sturton Street, Cambridge, CB1 2QF, UK
Aptivate is a not-for-profit company registered in England and Wales
wi
, Chris.
--
Aptivate | http://www.aptivate.org | Phone: +44 1223 967 838
Citylife House, Sturton Street, Cambridge, CB1 2QF, UK
Aptivate is a not-for-profit company registered in England and Wales
with company number 04980791.
--
You received this message because you are subscribed to the Google
220 (override the
field and add south to your project) which isn't currently possible.
Cheers, Chris.
--
Aptivate | http://www.aptivate.org | Phone: +44 1223 967 838
Future Business, Cam City FC, Milton Rd, Cambridge, CB4 1UY, UK
Aptivate is a not-for-profit company registered in England and
n the
test_runner.test_discover_runner.DiscoverRunnerTest.test_file_path test
- that test apparently needs to isolate itself better by setting the CWD
for the duration of the test, or something similar. Mind filing a bug? I
should be able to take a look soon.
Done, thanks: https://code.djangoproject.com/ticket/20449
Cheers,
--settings=tests.travis_configs.test_postgres_nogis \
transactions.tests.AtomicInsideTransactionTests
Is this expected behaviour? It's rather counter-intuitive to me.
Cheers, Chris.
--
Aptivate | http://www.aptivate.org | Phone: +44 1223 967 838
Future Business, Cam City FC, Milton Rd, Cambridge, CB4 1UY, UK
Aptivate is a
On Sat, 18 May 2013, Chris Wilson wrote:
I think Travis is unhappy about something in this commit. Any ideas?
==
ERROR: test_file_path (test_runner.test_discover_runner.DiscoverRunnerTest
n
loadTestsFromName
module = __import__('.'.join(parts_copy))
ImportError: Import by filename is not supported.
<https://next.travis-ci.org/aptivate/django/jobs/7275360>
Cheers, Chris.
--
Aptivate | http://www.aptivate.org | Phone: +44 1223 967 838
Future Business, Cam City FC, Mi
avis-ci/issues/902
branches:
only:
- master
- travisci
I guess this would only cause problems if anyone's building an old branch,
or their own fork of django, in Travis. In which case they'll have to
resolve the merge conflict, and again whenever we change the .travi
ten it is being closed". Using anything else that
doesn't close the ticket just lets it hang out as cruft.
I'm OK with it being a closed state, if that helps. I'd just prefer a
slightly friendlier name for it.
Cheers, Chris.
--
Aptivate | http://www.aptivate.org | Phon
SION. I could suggest some more:
ITSAPONY? JUSTIFY?
I think we're lucky to have a community where it's possible to persuade
the BDFLs to change their minds, and unlucky to have an unfriendly-looking
bug tracker which dissuades people from trying.
Cheers, Chris.
--
Aptivate | h
ket as evidence for a desire for the feature, and hence its
usefulness. And voting on the ticket instead of here saves a lot of "me
too" noise on the mailing list.
Cheers, Chris.
--
Aptivate | http://www.aptivate.org | Phone: +44 1223 967 838
Future Business, Cam City FC, Milton Rd, Cambr
d.aptivate.org/2010/11/26/hibernate-ejb-and-the-unique-constraint/
It's always possible to have an out-of-date model object in memory with
Django, with or without refresh() (which just allows us to update it
manually). I suggest we let that sleeping dog lie.
Cheers, Chris.
--
Aptivate | h
p// and so on.
Then it comes to Django. How do you do that?
I put the type in the URL to make it obvious. That doesn't harm SEO and
makes your URL routing clearer. For example:
/product//
/category//
/occasion//
But that's getting into django-users territory.
Cheers, Chris
them in the
first place).
Cheers, Chris.
--
Aptivate | http://www.aptivate.org | Phone: +44 1223 967 838
Future Business, Cam City FC, Milton Rd, Cambridge, CB4 1UY, UK
Aptivate is a not-for-profit company registered in England and Wales
with company number 04980791.
--
You received this
sue, and I couldn't find one from a
> quick search, so feel free to open one. The approach described by the OP
> seems reasonable, so if you want to provide a patch as well, feel free.
>
> Yours,
> Russ Magee %-)
>
> On Wed, Jan 9, 2013 at 11:37 PM, Chris Proto
> &g
1 - 100 of 258 matches
Mail list logo
