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 n
[ ] 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 dep
On Wed, Apr 23, 2014 at 11:09 PM, mmarco 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 Python package
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 py
Also, ccache is your friend if you want to cut compile times a lot
here (and elsewhere).
On Wed, Apr 23, 2014 at 2:46 PM, Nathann Cohen wrote:
> If it can help, here is my "gtmp" function :
>
> function gtmp
> {
> cd ~/sage
> git checkout d
> git branch -D tmp
> git checkout -b tm
On Wednesday, April 23, 2014 6:46:50 PM UTC-4, William 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
> Pyt
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.
See https://pypi.python.org/pypi/pip
pip is amazing -- you can actual
I agree that it is tricky. There is no need to cache the unique output
since it itself is cached by being unique. This is testable with some
effort; in doctest mode the memoization decorators should performs some
additional testing. Takes some work to write but no conceptual problem.
Also, I th
(this thread follows
https://groups.google.com/d/topic/sage-devel/awjiHPph6f8/discussion)
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@go
Please guys.. Answer this thread, this is a bad problem. It is important to
do something about it... :-/
Nathann
On Sunday, April 6, 2014 7:21:18 PM UTC+2, Nils Bruin wrote:
>
> The following paradigm happens for
> "sage.combinat.posets.posets.FinitePoset" and their "linear_extensions",
> but
If it can help, here is my "gtmp" function :
function gtmp
{
cd ~/sage
git checkout d
git branch -D tmp
git checkout -b tmp d &&
git pull trac "$1"
}
gtmp public/whatever fetches the branches and merges it with the develop
branch (named d on my computer). No pain involved, no
On Wed, Apr 23, 2014 at 11:31 PM, Kannappan Sampath wrote:
>
>
>
> On Wed, Apr 23, 2014 at 11:19 PM, Vincent Delecroix <
> 20100.delecr...@gmail.com> wrote:
>
>> Me again...
>>
>> If you correct the code, please provide a piece of code that does not
>> work with the current implementation (otherwi
On Wed, Apr 23, 2014 at 11:19 PM, Vincent Delecroix <
20100.delecr...@gmail.com> wrote:
> Me again...
>
> If you correct the code, please provide a piece of code that does not
> work with the current implementation (otherwise, it can not be
> considered as a bug).
>
> Well, OK. My fault. Pass any
That seemed to work, thanks.
El miércoles, 23 de abril de 2014 18:24:57 UTC+2, Volker Braun escribió:
>
> Its not a problem with ncurses but with your bash crapping out if
> LD_LIBRARY_PATH is set.Delete the Sage ncurses libraries and continue
> building.
>
--
You received this message becaus
Actually the whole function can be done with one line
{{{
blocks = [[i for i in xrange(M.nrows()) if M[i,j]] for j in
xrange(M.ncols())]
}}}
2014-04-23 19:49 UTC+02:00, Vincent Delecroix <20100.delecr...@gmail.com>:
> Me again...
>
> If you correct the code, please provide a piece of code that
Me again...
If you correct the code, please provide a piece of code that does not
work with the current implementation (otherwise, it can not be
considered as a bug).
If you do correct it please change
{{{
v = len(M.rows())
b = len(M.columns())
}}}
by
{{{
v = M.nrows()
b = M.ncols()
:-)
On Wed, Apr 23, 2014 at 11:07 PM, Vincent Delecroix <
20100.delecr...@gmail.com> wrote:
> What is the problem? You just copy/paste the definition of a function.
>
> 2014-04-23 19:31 UTC+02:00, Kannappan Sampath :
> > Hello group,
> >
> > I think this is probably an embarrassing bug:
> >
> >
What is the problem? You just copy/paste the definition of a function.
2014-04-23 19:31 UTC+02:00, Kannappan Sampath :
> Hello group,
>
> I think this is probably an embarrassing bug:
>
> def IncidenceStructureFromMatrix(M, name=None):
> """
> Builds and incidence structure from a matrix.
Hello group,
I think this is probably an embarrassing bug:
def IncidenceStructureFromMatrix(M, name=None):
"""
Builds and incidence structure from a matrix.
INPUT:
- ``M`` -- a binary matrix. Creates a set of "points" from the rows and a
set of "blocks" from the columns.
I see. Thanks Volker.
Are there any concrete plans for making the build system better ?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@goo
Its not a problem with ncurses but with your bash crapping out if
LD_LIBRARY_PATH is set.Delete the Sage ncurses libraries and continue
building.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving
I just pulled the last development release, and when compiling, i got this
error.
Someone can reproduce?
Host system:
Linux localhost 3.10.17-gentoo #2 SMP PREEMPT Tue Dec 10 22:34:37 CET 2013
x86_64 Intel(R) Core(TM)2 Duo CPU T9300 @ 2.50GHz GenuineIntel GNU/Linux
*
1) is the normal way, your first parent is your development branch. That
is, HEAD~ is your previous commit etc.
2) is a bit wonky but permissible if you want to.
The build system needs to be changed to not look at filesystem timestamps
but repository information. Once that is fixed there is no
Hi,
I was working on a ticket on my local branch X based on an old Sage
version. Let say that my develop is up to date and my HEAD is
currently at develop. I want to merge X to be up to date and see two
ways to do this
1)
{{{
git checkout X
git merge develop
}}}
2)
{{{
git checkout -b Y
git merg
On Wed, Apr 23, 2014 at 4:06 PM, Kannappan Sampath wrote:
> Thank you all for suggesting that I take a look at GIT. I think I feel
> better now. But, still I have gotten some questions. I am trying to review
> 16091.
>
> I have checked out the ncohen's 16091 branch and have it as a local
> branch.
>From the preview of the updated docs in the already-mentioned ticket #16030:
http://boxen.math.washington.edu/home/vbraun/doc/developer/walk_through.html#rebuilding-sage
On Wednesday, April 23, 2014 3:06:44 PM UTC+1, KnS wrote:
>
> Thank you all for suggesting that I take a look at GIT. I think
On Wednesday, April 23, 2014 4:48:32 PM UTC+2, leif wrote:
>
> Jean-Pierre Flori wrote:
> > On Tuesday, April 22, 2014 5:42:44 PM UTC+2, leif wrote:
> > >> (Release of 4.9.0 is scheduled for Tuesday, so we'll presumably
> > face it
> > >> soon in some distros.)
> >
> > I'm upd
Jean-Pierre Flori wrote:
On Tuesday, April 22, 2014 5:42:44 PM UTC+2, leif wrote:
>> (Release of 4.9.0 is scheduled for Tuesday, so we'll presumably
face it
>> soon in some distros.)
I'm updating an Ubuntu LTS and it seems gcc 4.9 is shipped with it (I
did not trigger its install m
Hi Sage Devs,
There's more information about confirmed participants for SD58 and
SD59 in June in Seattle now. There's still room for more people.
http://wiki.sagemath.org/days58, http://wiki.sagemath.org/days59
Keith Clawson (Seattle)
Miguel Marco-Buzunariz (Germany)
Marcos Rodríguez Rodríguez
Thank you all for suggesting that I take a look at GIT. I think I feel
better now. But, still I have gotten some questions. I am trying to review
16091.
I have checked out the ncohen's 16091 branch and have it as a local branch.
I would like to now let sage now that there has been a change in its
Yo !!
> The thing is, it may be very useful for someone who has figured out how to
> construct new t-designs for example.
We should aim at implementing all cnstruction theorems we can find. It
has to be there, invisbly working behind the scene :-P
> I shall try to get this done.
On Apr 23, 2014, at 1:41 PM, Nathann Cohen wrote:
> Hello !!
>
>> And, we still have not thought about the nomenclature... :-) May be change
>> the
>> Hadamard design to HadamardTwoDesign and implement these as
>> HadamardThreeDesign?
>
> Hmmm... Well, I would vote for HadamardDes
I've created http://trac.sagemath.org/ticket/16218 for the free objects
and http://trac.sagemath.org/ticket/16219 for the algebras catalog.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails f
Hi,
anyone up for reviewing http://trac.sagemath.org/ticket/15976 which adds an
integer lattice class (discussed here before)?
Cheers,
Martin
signature.asc
Description: This is a digitally signed message part.
On Tuesday, April 22, 2014 5:42:44 PM UTC+2, leif wrote:
>
> leif wrote:
> > leif wrote:
> >> Is there already a ticket for issues with GCC 4.9?
> >
> > I think I'll open a (small) metaticket soon.
>
> Did so: http://trac.sagemath.org/ticket/16208
>
> Although it's (currently) not a metatic
Dear Miguel,
Memory is not the sole limitation here. The main problem is that the worst
case time complexity is O(n^4). For instance, it took me several weeks of
computation to determine the hyperbolicity of the latest CAIDA maps (2012
and 2013).
There is currently no exact algorithm for comput
Hello !!
> And, we still have not thought about the nomenclature… :-) May be change the
> Hadamard design to HadamardTwoDesign and implement these as
> HadamardThreeDesign?
Hmmm... Well, I would vote for HadamardDesign and
Hadamard3Design/HadamardThreeDesign. Everybody seems to agree
On 2014-04-22 23:11, Dima Pasechnik wrote:
On 2014-04-22, Jeroen Demeyer wrote:
On 2014-04-21 10:10, Dima Pasechnik wrote:
this is not a normal extension, and apparently neither Pari nor GAP
can deal with it.
Pathetic...
Is it really so hard to implement, having the library of permutation
grou
38 matches
Mail list logo
