Can it handle non-python packages? Or the idea is to use it only for python
packages that need no compilation at all?
El jueves, 24 de abril de 2014 00:46:50 UTC+2, William escribió:
Hi,
There used to be a lot of confusion about which package manager /
installer one should use with python
On Wed, Apr 23, 2014 at 11:09 PM, mmarco mma...@unizar.es wrote:
Can it handle non-python packages?
No -- it is the standard package manager *for* Python.
Or the idea is to use it only for python packages that need no compilation at
all?
This question doesn't make sense to me, because many
[ ] Yes, make pip a standard part of Sage.
[ ] No, pip does not belong in Sage.
It depends: I would say Yes if the objective is to simplify the
install script (i.e. use pip for all our Python packages that are not
patched). Note that pip is very convenient and takes care of
versioning and
On Wed, Apr 23, 2014 at 03:46:50PM -0700, William Stein wrote:
[ ] Yes, make pip a standard part of Sage.
[ ] No, pip does not belong in Sage.
Definitely +1 on any step toward using standard package managers, and
this sounds like a nice one. Now which tools is most appropriate, I
have no
Hi Leif,
Do you have a URL for me of the bug / fixes?
https://bugs.launchpad.net/ubuntu/+source/gcc-4.6
Regards,
Jan
On 20 April 2014 16:26, leif not.rea...@online.de wrote:
Jan Groenewald wrote:
On 20 April 2014 14:50, leif not.rea...@online.de
mailto:not.rea...@online.de wrote:
On 2014-04-24 00:46, William Stein wrote:
Hi,
There used to be a lot of confusion about which package manager /
installer one should use with python -- easy_install? setuptools?
etc.
Now the choice is clear: pip -- A tool for installing and managing
Python packages.
Does pip supersede
Hi
On 24 April 2014 09:44, Jeroen Demeyer jdeme...@cage.ugent.be wrote:
On 2014-04-24 00:46, William Stein wrote:
Hi,
There used to be a lot of confusion about which package manager /
installer one should use with python -- easy_install? setuptools?
etc.
Now the choice is clear: pip
Question: would this make it possible to automatically have certain
python packages installed when Sage builds (after building its python
of course), perhaps from a list kept in a config file in .sage/ ? I
have a list of packages I use a lot (for the lmfdb project), e.g.
pymongo, and it is a
Hi,
I was reading #16216 and I was wondering whether
1) it is possible instead of a branch, to provide a simple script that
would be applied to the source files
2) it is possible to provide a simple script that would be tested for
each future branch merge (typically after #16216 it would be
That could / should be part of a more comprehensive approach: check for
PEP8 / other guideline violations.
Such a script might be supplied by Sage. It could even be a git pre-commit
hook (but I would consider this too extreme :-)
Wilfried
--
You received this message because you are
Jan Groenewald wrote:
Do you have a URL for me of the bug / fixes?
https://bugs.launchpad.net/ubuntu/+source/gcc-4.6/+bug/968766
https://bugs.launchpad.net/ubuntu/+source/gcc-4.6/+bug/972648
-leif
On 20 April 2014 16:26, leif not.rea...@online.de
mailto:not.rea...@online.de wrote:
Hi Keith!
On Tue, Apr 15, 2014 at 01:31:07PM -0700, Keith Clawson wrote:
I just finished moving wiki.sagemath.org from boxen to a dedicated virtual
machine. The only noticeable change should be that I renamed
MyStartingPage to SageWiki (there's a redirect so this shouldn't
I guess some package management would be an improvement from the
present situation. the fact it only works for python packages is a bit
half baked but it is a good step in my opinion.
As far as I can tell this means that once we have bootstrapped pip we
can simplify spkg-install for python
Hi
This seems to be a holdup:
Steve Langasek (vorlon) https://launchpad.net/%7Evorlon wrote on
2012-10-13:
#11https://bugs.launchpad.net/ubuntu/+source/gcc-4.6/+bug/972648/comments/11
The change that has been uploaded to precise-proposed looks appropriate for
an SRU, but this bug is missing
On Thursday, April 24, 2014 9:37:14 AM UTC+1, vdelecroix wrote:
1) it is possible instead of a branch, to provide a simple script that
would be applied to the source files
No
2) it is possible to provide a simple script that would be tested for
each future branch merge (typically
Thanks Volker.
2014-04-24 15:38 UTC+02:00, Volker Braun vbraun.n...@gmail.com:
On Thursday, April 24, 2014 9:37:14 AM UTC+1, vdelecroix wrote:
1) it is possible instead of a branch, to provide a simple script that
would be applied to the source files
No
1') Would it be possible to have
On Thursday, April 24, 2014 2:48:19 PM UTC+1, vdelecroix wrote:
1') Would it be possible to have access to the very last commit before
the stable version?
The last commit might always change before it is released, so i don't
really see why you want that. You can talk to me if your ticket
2014-04-24 16:10 UTC+02:00, Volker Braun vbraun.n...@gmail.com:
On Thursday, April 24, 2014 2:48:19 PM UTC+1, vdelecroix wrote:
1') Would it be possible to have access to the very last commit before
the stable version?
The last commit might always change before it is released, so i don't
On Thursday, April 24, 2014 12:43:05 AM UTC-4, Robert Bradshaw wrote:
Also, ccache is your friend if you want to cut compile times a lot
here (and elsewhere).
With regard to which, see http://trac.sagemath.org/ticket/14372 for the
opportunity to actually document this somewhere in the
On Saturday, 19 April 2014 11:46:21 UTC+1, KnS wrote:
Hello sage-devel:
I am trying to prepare a notebook for a SAGE demo at my institute. In
rying to compute the Galois group, I am stuck here. SAGE complains that I
have to install KASH while I already have KASH installed.
sage: K.a
On Thursday, April 24, 2014 4:01:07 PM UTC+1, vdelecroix wrote:
The point is that #16216 modifies 179 files (9.2% of the files in Sage
source code) in a somewhat trivial way. I am pretty sure that we can
not avoid merge conflicts. The real question is: what is the best
strategy for it to
Ok, I installed docutils and the page renders correctly now.
-Keith
On Thursday, April 24, 2014 2:42:20 AM UTC-7, Nicolas M. Thiéry wrote:
Hi Keith!
On Tue, Apr 15, 2014 at 01:31:07PM -0700, Keith Clawson wrote:
I just finished moving wiki.sagemath.org from boxen to a
Hi,
I just pulled the newest develop version and did make start. Now, I get
the error below. Am I again doing something wrong here?
Thanks for your help,
Christian
---
-- stumpc5@stumpc5:~/progs/sage$ sage
Why using make start instead of make?
2014-04-24 21:56 UTC+02:00, Christian Stump christian.st...@gmail.com:
Hi,
I just pulled the newest develop version and did make start. Now, I get
the error below. Am I again doing something wrong here?
Thanks for your help,
Christian
Why using make start instead of make?
(doing it currently, but it takes some time.) I thought that's the same,
except that I save the time of building the documentation. Isn't that right?
Thanks!
--
You received this message because you are subscribed to the Google Groups
sage-devel
Why using make start instead of make?
(doing it currently, but it takes some time.) I thought that's the same,
except that I save the time of building the documentation. Isn't that right?
okay, it finished -- but the error on startup remained... any ideas?
Thanks again, Christian
--
Hi Christian,
Please, put the log somewhere accessible to everybody.
From which version did you upgrade? Sometimes, the build system is not
smart enough and it is needed to do a make distclean and then
make... i.e. rebuilding Sage from scratch.
2014-04-24 22:34 UTC+02:00, Christian Stump
Please, put the log somewhere accessible to everybody.
From which version did you upgrade? Sometimes, the build system is not
smart enough and it is needed to do a make distclean and then
make... i.e. rebuilding Sage from scratch.
Thanks for your help! I attach the report -- I
Thanks for your help! I attach the report -- I upgraded from 6.2.beta4 if
I remember right. I will redo the make, but that will take until tomorrow
morning...
I just typed the last line of the crash report into google and see that it
was discussed before in sage-release:
29 matches
Mail list logo
