Re: 1.8 shipping invalid .py files in the startapp template

Damn, I meant to write "and not real packages" On Sunday, November 29, 2015 at 2:46:22 AM UTC+1, Florian Apolloner wrote: > > > > On Saturday, November 28, 2015 at 7:16:10 PM UTC+1, lamby wrote: >> >> > at least project_template would be missing etc >> >> Deliberately so; these are not invalid

Re: 1.8 shipping invalid .py files in the startapp template

On Saturday, November 28, 2015 at 7:16:10 PM UTC+1, lamby wrote: > > > at least project_template would be missing etc > > Deliberately so; these are not invalid .py files. > Yes, but by luck and/or accident. In the end they are still package data and real packages, so you should never run

Re: Fellow Report - November 28, 2015

Hello, sure do not want to pass the ticket https://code.djangoproject.com/ticket/25811? Please note the full comments of the ticket and give your opinion on the solution really that change for me would be, I need to bring a project to a second level separating several apps on the basis of

Fellow Report - November 28, 2015

I've also been coordinating the next round of fundraising with Adrienne which includes cleaning up the data for our existing donor records and making some improvements to the website for the next campaign. Triaged --- https://code.djangoproject.com/ticket/25799 - list_filter filtering

Re: Integrating Django with Tornado's web server

Hi Bastin, I know you addressed the question to bret, but i would like to suggest what i did , i actually used gevent-socketio with the pywsgi server . I did it a while ago so dont know if things are the same. If you find something better then do tell. On Wednesday, October 21, 2015 at 4:52:23

Re: 1.8 shipping invalid .py files in the startapp template

> I believe this is a new issue in 1.9, not 1.8 as the subject says, correct? Correct, apologies. (I meant to write "since 1.8" as "1.9" is either ambiguous or not released yet.) > Is the "man-page of pycompile you can exclude certain packages" suggestion some change we should make in

Re: 1.8 shipping invalid .py files in the startapp template

"Force" or "nudge" to upgrade pip? i.e. should Django not install with pip < some version? That seems controversial. Is the "man-page of pycompile you can exclude certain packages" suggestion some change we should make in Django? As long as we have some solution to avoid support queries about

Re: 1.8 shipping invalid .py files in the startapp template

If I am not mistaken 1.5.6 is still one of those versions which whould install from external sources etc… So from a security point of view I wanna force people to upgrade. Regarding purity: No it is not purity, as the PR already showed, at least project_template would be missing etc… Also

Re: 1.8 shipping invalid .py files in the startapp template

Yes, I know but it creates confusion for users and has resulted in at least two bug reports like https://code.djangoproject.com/ticket/25584. I suspect we'll see more reports and queries about it once 1.9 goes final so I'd like to avoid that as long as there isn't any downside to the proposed

Re: 1.8 shipping invalid .py files in the startapp template

> On Nov 28, 2015, at 11:03 AM, Tim Graham wrote: > > Claude said, "I also encountered this error when using pip 1.5.6 (default > version in Debian stable)." I guess at least some people might not want to > upgrade system packages. > > Is your main opposition to the

Re: 1.8 shipping invalid .py files in the startapp template

Claude said, "I also encountered this error when using pip 1.5.6 (default version in Debian stable)." I guess at least some people might not want to upgrade system packages. Is your main opposition to the change a "purity" one? Sure, we could add a pip version check, but I don't see any

Re: 1.8 shipping invalid .py files in the startapp template

I rather add a check to setup.py and tell people to upgrade pip On Saturday, November 28, 2015 at 1:46:48 PM UTC+1, Tim Graham wrote: > > I believe this is a new issue in 1.9, not 1.8 as the subject says, correct? > > I wouldn't mind seeing it fixed as old versions of pip report a > SyntaxError

Re: 1.8 shipping invalid .py files in the startapp template

I believe this is a new issue in 1.9, not 1.8 as the subject says, correct? I wouldn't mind seeing it fixed as old versions of pip report a SyntaxError when installing Django (this doesn't affect the install, but creates confusion for users and resulted in at least two bug reports like

Re: 1.8 shipping invalid .py files in the startapp template

Hi, Those packages/modules are clearly marked as package data (https://github.com/django/django/blob/master/setup.py#L26-L28), so imo it is a bug in Debian packaging (although I do understand that it might not be the easiest to fix…). According to the man-page of pycompile you can exclude

1.8 shipping invalid .py files in the startapp template

Hi, I sent this first as a pull request — talk is cheap, code is better, etc. — but now feel I should I have posted here first. The underlying issue is that Debian packages unconditionally byte-compile .py files under dist-packages upon installation using `pycompile` and do not silence errors by