Dear Florian,
Thanks so much for your update/feedback.
I updated the update
here: https://github.com/elena/django-news-podcast/issues/1
Thanks again!
Elena
On Sunday, December 29, 2013 8:10:30 PM UTC+11, Florian Apolloner wrote:
>
> Just so we are all on the same page here (summarizing
Just so we are all on the same page here (summarizing discussions from IRC
etc):
* We are not going to support setuptools and distutils, this makes the
setupprocess difficult to debug and test imo.
* Given Donald's "okay" we might switch to setuptools completely
* There seems to be a bug in
On Dec 4, 2013, at 5:51 PM, Florian Apolloner wrote:
> On Wednesday, December 4, 2013 11:20:39 PM UTC+1, Donald Stufft wrote:
> entry points are kinda wonky with pip 1.4, pip 1.5 makes them sane. You would
> not need a Windows specific Wheel with pip 1.5
>
> Is there a
On Wednesday, December 4, 2013 11:20:39 PM UTC+1, Donald Stufft wrote:
>
> entry points are kinda wonky with pip 1.4, pip 1.5 makes them sane. You
> would not need a Windows specific Wheel with pip 1.5
>
Is there a test-pypi where I could upload Django packages to test this?
--
You received
On Dec 4, 2013, at 4:31 PM, Florian Apolloner wrote:
> Oh, one last thing (a few actually):
> How does 'entry_points' work with wheels?
> Do we need an extra wheel for windows just to get the wrappers right?
> Can we generate a windows wheel from *nix, or do we need a
Oh, one last thing (a few actually):
- How does 'entry_points' work with wheels?
- Do we need an extra wheel for windows just to get the wrappers right?
- Can we generate a windows wheel from *nix, or do we need a windows box?
Cheers,
Florian
On Wednesday, December 4, 2013 10:24:09
On Wednesday, December 4, 2013 8:24:49 PM UTC+1, Remram wrote:
>
> December 4 12:43, Florian Apolloner
>>
>> To my understanding of
>> https://github.com/pypa/pip/blob/develop/pip/req.py#L633 pip will use
>> setuptools for installing -- so why do you need setuptools in Django itself?
>>
> The
December 4 12:43, Florian Apolloner
>
> To my understanding of
> https://github.com/pypa/pip/blob/develop/pip/req.py#L633 pip will use
> setuptools for installing -- so why do you need setuptools in Django itself?
>
Hi Florian,
The point here is to use options that distutils doesn't offer,
Hi Remram,
On Wednesday, December 4, 2013 4:56:55 PM UTC+1, Remram wrote:
>
> November 24 14:37, Florian Apolloner
>>
>> I am pretty much against setuptools and given that pip is somewhat
>> becoming the defacto-standard to install stuff
>>
>
> I completely agree to this. And setuptools is an
November 24 14:37, Florian Apolloner
>
> I am pretty much against setuptools and given that pip is somewhat
> becoming the defacto-standard to install stuff
>
I completely agree to this. And setuptools is an important part of pip...
In fact, pip has a strong dependency on setuptools, and
Waylan is correct, but does not go far enough.
When one installs Python 3.3, the Python Launcher for Windows is also
installed. I install Python 3 even on systems where I do not (at present)
plan to use it, just to get the launcher. The launcher is the program which
should be associated with
On Sunday, November 24, 2013, Rémi Rampin wrote:
> Hi developers,
>
> On Windows, running the django-admin.py tool is painful[1], because
> .py scripts are not "executable". You might be able to run it using
> the full path (if Python is the default handler for .py files, which
> it really
The recommended build tool at the moment is setuptools.
It's up to the individual project to decide if they think the install story for
setutpools pre 3.4 is appropriate for them. This'll get better in general in
the future with MSI installers for setuptools and pip
> On Nov 24, 2013, at
Hi,
I am pretty much against setuptools and given that pip is somewhat becoming
the defacto-standard to install stuff; I'd ask Donald what can be done here
(cc'ed him). I don't think it's a good idea to fix this in Django since
this is imo a problem in Python itself.
Regards,
Florian
On
Hi developers,
On Windows, running the django-admin.py tool is painful[1], because
.py scripts are not "executable". You might be able to run it using
the full path (if Python is the default handler for .py files, which
it really shouldn't be). Most probably you'll need to copy it to your
project
15 matches
Mail list logo